Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1602896743.1260736398169.JavaMail.jira@brutus>
Date: Sun, 13 Dec 2009 20:33:18 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-651) Re-enable the storing of java objects
 in the database
In-Reply-To: <1964282168.1130361355487.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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-08-aa-dependencyRoutines.diff

Attaching derby-651-08-aa-dependencyRoutines.diff. This patch adds dependencies of routines on UDTs. The tests passed cleanly for me. Committed at subversion revision 890115.


Touches the following files:

M      java/engine/org/apache/derby/loc/messages.xml
M      java/shared/org/apache/derby/shared/common/reference/SQLState.java

New error message raised when a routine blocks the dropping of a UDT.


M      java/engine/org/apache/derby/iapi/sql/dictionary/TupleDescriptor.java
M      java/engine/org/apache/derby/iapi/sql/dictionary/TableDescriptor.java

Moved some reporting logic out of TableDescriptor up into its superclass so that the logic can be used by AliasDescriptor.


M      java/engine/org/apache/derby/iapi/sql/dictionary/AliasDescriptor.java

Made AliasDescriptor a dependent.


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

Logic to add and drop dependencies of routines on UDTs.


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

Regression tests for dependencies of routines on UDTs.


> 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, derby-651-07-aa-dependencyView.diff, derby-651-08-aa-dependencyRoutines.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.