You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/02/01 19:27:08 UTC
[jira] Created: (DERBY-3377) Network Client/Server should use
sqlType instead of locator value to determine if lob was sent by
locator/value
Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value
---------------------------------------------------------------------------------------------------------------
Key: DERBY-3377
URL: https://issues.apache.org/jira/browse/DERBY-3377
Project: Derby
Issue Type: Bug
Components: Network Client, Network Server
Reporter: Kathey Marsden
Priority: Minor
This issue came up during the fix for DERBY-3243. Currently network server does not send the correct sqlType for locators. It sends DB2_SQLTYPE_BLOB or DB2_SQLTYPE_CLOB instead of DB2_SQLTYPE_BLOB_LOCATOR or DB2_SQLTYPE_CLOB_LOCATOR so the client's only way of determining whether it is getting a lob by value or locator is to look at the locator/extended length field and use that to branch its logic. It would be cleaner moving foward to use the sqlType to branch this logic, but there would have to be version specific handling to allow it to work the old way when communicating with older versions.
The sqlType is sent as part of the SQLDAGRP in DRDAConnThread.writeSQLDAGRP() in the
server code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3377) Network Client/Server should use
sqlType instead of locator value to determine if lob was sent by
locator/value
Posted by "Tiago R. Espinha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tiago R. Espinha updated DERBY-3377:
------------------------------------
Urgency: Low
Bug behavior facts: [Embedded/Client difference]
Triaged for 10.5.2.
Assigned low urgency and checked embedded/client difference as only the network server is mentioned.
> Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3377
> URL: https://issues.apache.org/jira/browse/DERBY-3377
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.1.3
> Reporter: Kathey Marsden
> Priority: Minor
>
> This issue came up during the fix for DERBY-3243. Currently network server does not send the correct sqlType for locators. It sends DB2_SQLTYPE_BLOB or DB2_SQLTYPE_CLOB instead of DB2_SQLTYPE_BLOB_LOCATOR or DB2_SQLTYPE_CLOB_LOCATOR so the client's only way of determining whether it is getting a lob by value or locator is to look at the locator/extended length field and use that to branch its logic. It would be cleaner moving foward to use the sqlType to branch this logic, but there would have to be version specific handling to allow it to work the old way when communicating with older versions.
> The sqlType is sent as part of the SQLDAGRP in DRDAConnThread.writeSQLDAGRP() in the
> server code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3377) Network Client/Server should use
sqlType instead of locator value to determine if lob was sent by
locator/value
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3377:
----------------------------------
Affects Version/s: 10.4.0.0
10.3.1.4
10.3.2.1
> Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3377
> URL: https://issues.apache.org/jira/browse/DERBY-3377
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> This issue came up during the fix for DERBY-3243. Currently network server does not send the correct sqlType for locators. It sends DB2_SQLTYPE_BLOB or DB2_SQLTYPE_CLOB instead of DB2_SQLTYPE_BLOB_LOCATOR or DB2_SQLTYPE_CLOB_LOCATOR so the client's only way of determining whether it is getting a lob by value or locator is to look at the locator/extended length field and use that to branch its logic. It would be cleaner moving foward to use the sqlType to branch this logic, but there would have to be version specific handling to allow it to work the old way when communicating with older versions.
> The sqlType is sent as part of the SQLDAGRP in DRDAConnThread.writeSQLDAGRP() in the
> server code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3377) Network Client/Server should use
sqlType instead of locator value to determine if lob was sent by
locator/value
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3377:
-----------------------------------
Issue Type: Improvement (was: Bug)
Bug behavior facts: (was: [Embedded/Client difference])
Labels: LOB (was: )
> Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3377
> URL: https://issues.apache.org/jira/browse/DERBY-3377
> Project: Derby
> Issue Type: Improvement
> Components: Network Client, Network Server
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.1.3
> Reporter: Kathey Marsden
> Priority: Minor
>
> This issue came up during the fix for DERBY-3243. Currently network server does not send the correct sqlType for locators. It sends DB2_SQLTYPE_BLOB or DB2_SQLTYPE_CLOB instead of DB2_SQLTYPE_BLOB_LOCATOR or DB2_SQLTYPE_CLOB_LOCATOR so the client's only way of determining whether it is getting a lob by value or locator is to look at the locator/extended length field and use that to branch its logic. It would be cleaner moving foward to use the sqlType to branch this logic, but there would have to be version specific handling to allow it to work the old way when communicating with older versions.
> The sqlType is sent as part of the SQLDAGRP in DRDAConnThread.writeSQLDAGRP() in the
> server code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.