db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-716) Re-enable VTIs
Date Thu, 19 Apr 2007 17:05:20 GMT

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

Daniel John Debrunner commented on DERBY-716:

Rick > If we think that stubbing out this interface for all platforms is too onerous, we
could consider supplying a JDBC4 template in a demo directory--the user could prune that template
back to a JSR169 compliant form if necessary. We could even provide templates for all the
JDBC levels we support--that does not seem like a lot of work for us.

It's not that it's a lot of work for anyone, it moves to a model where an application that
wants to support multiple JDBC environments has two unpleasant choices:
   - have a Java class with multiple versions (doesn't fit well into the Java development

  - have different versions of the SQL schema for different platforms (different create function
statements that point to different java classes)

Maybe that's not a huge concern, Derby could just say it has the facility to present a JDBC
ResultSet as a virtual table and it's the user's problem if they want to support multiple

> 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
>         Attachments: 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.

View raw message