[
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-11-aa-dropSchema.diff
Attaching derby-651-11-aa-dropSchema.diff. This patch prevents you from
dropping a schema if it contains any types. I also noticed that it was possible
to drop schemas which contained routines. I have made that illegal too.
Regression tests passed for me. Committed at subversion revision 892485.
Basically, SYSALIASES is now not allowed to contain any rows that refer to the
schema which is about to be dropped. Touches the following files:
M java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java
This is the code which enforces the rule that a schema must be empty before you
drop it.
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/GeneratedColumnsHelper.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/UDTPermsTest.java
New test to verify that a schema may not hold any routines or types if you are
going to drop it.
M java/testing/org/apache/derbyTesting/junit/JDBC.java
Added a little logic so that UDTs are dropped along with routines when cleaning
out a test schema.
> 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, 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.
