You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2007/10/10 17:35:51 UTC
[jira] Updated: (DERBY-716) Re-enable VTIs
[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-716:
--------------------------------
Attachment: derby-716-10-datatypesCollation-aa.diff
Attaching derby-716-10-datatypesCollation-aa.diff. This adds tests verifying the following:
1) Make sure that Derby calls the expected getXXX() method for each legal datatype in the rowset returned by a table function.
2) Make sure that string columns in the returned rowset have the expected collation (described in the previous comment).
The second test uncovered a bug: we were always applying BASIC collation to string columns in the returned rowsets. This patch fixes that bug.
Touches the following files:
M java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java
M java/engine/org/apache/derby/catalog/types/TypeDescriptorImpl.java
Fix for the collation bug.
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/TableFunctionTest.java
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/StringArrayVTI.java
New tests.
> Re-enable VTIs
> --------------
>
> Key: DERBY-716
> URL: https://issues.apache.org/jira/browse/DERBY-716
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-716-01-basic-aa.diff, derby-716-02-DatabaseMetaData-aa.diff, derby-716-03-DatabaseMetaData-aa.diff, derby-716-04-Optimizer-aa.diff, derby-716-05-PublicAPI-aa.diff, derby-716-06-TestEncoding-aa.diff, derby-716-07-dblook-aa.diff, derby-716-08-upgrade-aa.diff, derby-716-09-upgradeLocalization-aa.diff, derby-716-10-datatypesCollation-aa.diff, functionTables.html, functionTables.html, functionTables.html
>
>
> Cloudscape used to expose Virtual Table Interfaces, by which any class which implemented ResultSet could be included in a query's FROM list. Derby still exposes a number of these VTIs as diagnostic tools. However, Derby now prevents customers from declaring their own VTIs. The parser raises an error if a VTI's package isn't one of the Derby diagnostic packages.
> This is a very powerful feature which customers can use to solve many problems. We should discuss the reasons that it was disabled and come up with a plan for putting this power back into our customers' hands.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.