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, 05 Feb 2010 18:44:28 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-13-aa-tableFunctionColumns.diff

Attaching derby-651-13-aa-tableFunctionColumns.diff. This patch makes it possible to use UDTs
as columns in the ResultSets returned by table functions. Regression tests are running.

Touches the following files:

--------

M      java/engine/org/apache/derby/impl/sql/compile/QueryTreeNode.java

Added logic for binding row multi sets which contain UDT columns.


--------

M      java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java

Always re-bind the return value of a function, even if it is not itself a UDT. This is because
the return type could be a row multi set which has a UDT column.


--------

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

Add logic to create dependencies on UDT-typed columns in table functions.


--------

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

Added a test case to verify that UDTs can be columns in table functions.


> 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,
derby-651-09-ac-usagePrivilege.diff, derby-651-10-aa-usageTriggers.diff, derby-651-11-aa-dropSchema.diff,
derby-651-12-ab-metadata.diff, derby-651-13-aa-tableFunctionColumns.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