Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4491

The network client changes UDTs into Strings and returns their type as LONGVARBINARY.


    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s:,,,,,,,,,,,,,,
    • Fix Version/s:
    • Component/s: JDBC
    • Issue & fix info:
      Patch Available
    • Bug behavior facts:
      Embedded/Client difference


      This is a pre-existing bug which seems to have been with Derby since the beginning. Some of the columns in the system tables (e.g., SYS.SYSALIASES.ALIASINFO) contain objects. If you select these columns:

      1) In the embedded client you will get the correct results. You will get the objects in these columns. In addition, the ResultSetMetaData for these columns will correctly report that the columns have type JAVA_OBJECT and will give a reasonable type name (the class name for the object in the column).

      2) However, in the network client, you will get the wrong results. ResultSet.getObject() will return Strings rather than the original objects. In addition, the ResultSetMetaData for these columns will incorrectly report that their type is LONGVARBINARY.


        1. derby-4491-01-ab-networkTransport.diff
          74 kB
          Rick Hillegas
        2. derby-4491-01-ad-networkTransport.diff
          96 kB
          Rick Hillegas
        3. derby-4491-02-aa-supportsUDTs.diff
          0.5 kB
          Kristian Waagan

          Issue Links



              • Assignee:
                rhillegas Rick Hillegas
                rhillegas Rick Hillegas
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: