1. Derby
  2. DERBY-3377

Network Client/Server should use sqlType instead of locator value to determine if lob was sent by locator/value


    • Urgency:


      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.

        Issue Links


          Kathey Marsden created issue -
          Kathey Marsden made changes -
          Field Original Value New Value
          Link This issue is related to DERBY-3243 [ DERBY-3243 ]
          Kathey Marsden made changes -
          Affects Version/s [ 12312590 ]
          Affects Version/s [ 12312876 ]
          Affects Version/s [ 12312540 ]
          Tiago R. Espinha made changes -
          Bug behavior facts [Embedded/Client difference]
          Urgency Low
          Kristian Waagan made changes -
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          Bug behavior facts [Embedded/Client difference]
          Labels LOB
          Kathey Marsden made changes -
          Labels LOB LOB derby_triage10_9
          Gavin made changes -
          Workflow jira [ 12422553 ] Default workflow, editable Closed status [ 12796929 ]


            • Assignee:
              Kathey Marsden
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: