[ http://issues.apache.org/jira/browse/DERBY-651?page=comments#action_12356028 ]
Satheesh Bandaram commented on DERBY-651: ----------------------------------------- I think this "bug" needs to be marked as Enhancement... Derby never had capability to store Java objects, so this should be seen as an enhancement request. SQL specification Part 13:SQL Routines and Types Using the Java Programming Language (SQL/JRT) is the standard way to add java objects. > Re-enable the storing of java objects in the database > ----------------------------------------------------- > > Key: DERBY-651 > URL: http://issues.apache.org/jira/browse/DERBY-651 > Project: Derby > Type: Bug > Components: SQL > Reporter: Rick Hillegas > > 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, cumbersom as it is, would do. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
