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] Updated: (DERBY-651) Re-enable the storing of java objects in the database
Date Fri, 11 Dec 2009 21:36:18 GMT

     [ https://issues.apache.org/jira/browse/DERBY-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-651:
--------------------------------

    Attachment: derby-651-06-aa-dropTable.diff

Attaching derby-651-06-aa-dropTable.diff. This addresses the bug which Knut discovered: if
you drop a table which depends on a UDT, the dependency arc from the table to the UDT is not
dropped. We were only dropping the arcs when we dropped individual columns from the table.
Tests passed cleanly for me. Committed at subversion revision 889822.

The fix was to make the DROP TABLE logic call the same arc-dropping code as the ALTER TABLE
logic calls. That logic was modified slightly to handle the DROP TABLE case.

Touches the following files:

M      java/engine/org/apache/derby/impl/sql/execute/DDLConstantAction.java

Changes the arc-dropping code to handle DROP TABLE. Changes the signature of the arc-dropping
method.


M      java/engine/org/apache/derby/impl/sql/execute/DropTableConstantAction.java

Calls that logic for DROP TABLE.


M      java/engine/org/apache/derby/impl/sql/execute/CreateTableConstantAction.java
M      java/engine/org/apache/derby/impl/sql/execute/AlterTableConstantAction.java

Accounts for the new signature of the arc-dropping method.


M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/UDTTest.java

Some regression tests to verify that the bug is fixed.


> Re-enable the storing of java objects in the database
> -----------------------------------------------------
>
>                 Key: DERBY-651
>                 URL: https://issues.apache.org/jira/browse/DERBY-651
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-651-01-aa-basicCreateDropType.diff, derby-651-02-af-udtColumnsRetvalsParams.diff,
derby-651-03-aa-udttestInstability.diff, derby-651-04-aa-javadoc.diff, derby-651-05-ac-dependencyTable.diff,
derby-651-06-aa-dropTable.diff, UserDefinedTypes.html, UserDefinedTypes.html, UserDefinedTypes.html,
UserDefinedTypes.html
>
>
> 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.

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