Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0
-
Patch Available
-
Embedded/Client difference
Description
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.
Attachments
Attachments
Issue Links
- is related to
-
DERBY-4688 With Derby 10.6 and higher, selecting object columns from system tables ERROR XN020: Error marshalling or unmarshalling a user defined type
- Open
-
DERBY-4499 Compiler error when preparing a procedure call with an output parameter of user defined type.
- Closed
-
DERBY-4516 The SanityManager is included in the common arm of the codeline but a use of it in client code gave rise to a sealing violation in AssertFailureTest when run against insane jars.
- Closed
- relates to
-
DERBY-6888 Large User-Defined Types break Network Client
- Open
-
DERBY-651 Re-enable the storing of java objects in the database
- Closed