db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-716) Re-enable VTIs
Date Mon, 24 Sep 2007 07:06:52 GMT

    [ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529787
] 

Knut Anders Hatlen commented on DERBY-716:
------------------------------------------

In this part of the patch

@@ -10136,6 +10136,8 @@
 	    ( <COMMA> functionTableReturnColumn( names, types ) ) *
 	<RIGHT_PAREN>
 	{
+        checkVersion( DataDictionary.DD_VERSION_DERBY_10_4, "table functions");
+
 		columnCount = names.size();
 		nameArray = new String[ columnCount ];
 		names.toArray( nameArray );

would it be better to replace "table functions" with "CREATE FUNCTION ... RETURNS TABLE"?
I think this would look better in the message since it puts quotes around the string (Use
of '{0}' requires database to be upgraded from...). It would also look better in the localized
messages since the SQL keywords are the same in all locales, whereas the term "table functions"
would need to be translated.

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


Mime
View raw message