[DERBY-651] Re-enable the storing of java objects in the database

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.6.1.0
• Component/s: SQL
• Issue & fix info: Patch Available
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 27/Oct/05 06:15
• Updated: 02/May/13 02:29
• Resolved: 16/Apr/10 16:40

Description

Islay Symonette, in an email thread called "Storing Java Objects in a table" on October 26, 2005 requests the ability to store java objects in the database.

Old releases of Cloudscape allow users to declare a column's type to be a Serializable class. This feature was removed from Derby because the syntax was non-standard. However, most of the machinery to support objects serialized to columns is still in Derby and is even used in system tables. We need to agree on some standard syntax here and re-expose this useful feature. Some subset of the ANSI adt syntax, cumbersome as it is, would do.

Issue Links

• incorporates: DERBY-4469 Fix the CASTing behavior of UDTs
• incorporates: DERBY-4470 Forbid ordering operations on UDTs
• incorporates: DERBY-4499 Compiler error when preparing a procedure call with an output parameter of user defined type.
• incorporates: DERBY-4484 Add import/export support for UDTs.
• incorporates: DERBY-4485 Add dblook support for UDTs.
• is depended upon by: DERBY-4572 Documentation needed for user-defined types
• is related to: DERBY-4491 The network client changes UDTs into Strings and returns their type as LONGVARBINARY.
• is related to: DERBY-4580 Cannot use dblook on soft-upgraded database: Table/View 'SYS.SYSSEQUENCES' does not exist.