db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3377) Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value
Date Fri, 01 Feb 2008 18:27:08 GMT
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.


Mime
View raw message