db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-651) Re-enable the storing of java objects in the database
Date Thu, 27 Oct 2005 14:21:57 GMT
     [ http://issues.apache.org/jira/browse/DERBY-651?page=all ]

Rick Hillegas updated DERBY-651:

    type: New Feature  (was: Bug)

Thanks, Satheesh. You're right, this is an enhancement.

> 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: New Feature
>   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:
For more information on JIRA, see:

View raw message