db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4491) The network client changes UDTs into Strings and returns that their type is LONGVARBINARY.
Date Tue, 22 Dec 2009 16:26:29 GMT
The network client changes UDTs into Strings and returns that their type is LONGVARBINARY.
------------------------------------------------------------------------------------------

                 Key: DERBY-4491
                 URL: https://issues.apache.org/jira/browse/DERBY-4491
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.5.3.0, 10.5.2.0, 10.5.1.1, 10.4.2.0, 10.4.1.3, 10.3.3.0, 10.3.2.1,
10.3.1.4, 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
            Reporter: Rick Hillegas


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.

-- 
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