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] Commented: (DERBY-716) Re-enable VTIs
Date Thu, 19 Apr 2007 18:42:15 GMT

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

Rick Hillegas commented on DERBY-716:

Dan> 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: 

I think that Øystein ran some experiments using Derby 10.1 (supporting JDBC3) on Java 6 (which
defines JDBC4). I think that Derby's JDBC3 ResultSets worked fine on Java 6 because the testing
application never called JDBC4-specific methods. I'm cautiously hopeful that an application
which needs to run on multiple VM revs can succeed as long as it codes to the least-common

I don't have any experience trying to run the same code on Java SE and Java ME. I have only
very limited experience trying to code an application to run both places. My limited experience
suggests that most people in this situation will end up writing a portablitliy layer, or even
two implementations because desktop users will refuse to live with the limitations imposed
by by the small-device environment.

> 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