[jira] Updated: (DERBY-3377) Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value

["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.