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] Updated: (DERBY-4932) Move the StringColumnVTI to the public api
Date Thu, 09 Dec 2010 20:18:00 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-4932:

    Attachment: derby-4932-05-ab-addJDBC4.0versions.diff

Attaching derby-4932-05-ab-addJDBC4.0versions.diff. This patch implements Knut's suggestion
of creating a non-abstract superclass of VTITemplate. Very sneaky. I will run regression tests.

With this patch, you should be able to compile under both Java 5 and Java 6 when you extend
VTITemplate and StringColumnVTI. There should be no need to add JDBC 4.1 methods to these
classes either.

The public api will include VTITemplate and StringColumnVTI.

After applying these changes, I was able to use both the Java 5 and Java 6 compilers to build
two classes which extend StringColumnVTI: PMDWrapper.java (see DERBY-4927) and RSMDWrapper.java
(see DERBY-4926). I was also able to use both compilers to build a simple class which extends

Touches the following files:


A      java/engine/org/apache/derby/vti/VTITemplateBase.java

New complete implementation of the JDBC 3.0 ResultSet.


M      java/engine/org/apache/derby/vti/VTITemplate.java

Abstract subclass


M      java/engine/org/apache/derby/vti/build.xml

Adds VTITemplateBase to the JDBC 3.0 build.

> Move the StringColumnVTI to the public api
> ------------------------------------------
>                 Key: DERBY-4932
>                 URL: https://issues.apache.org/jira/browse/DERBY-4932
>             Project: Derby
>          Issue Type: Improvement
>          Components: Javadoc, SQL, Tools
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>            Priority: Minor
>         Attachments: derby-4932-01-aa-exposeVTITemplate.diff, derby-4932-02-aa-moveStringColumnVTI.diff,
derby-4932-02-ab-moveStringColumnVTI.diff, derby-4932-03-aa-useInMemoryDBinDemos.diff, derby-4932-04-aa-retireDemoVersion.diff,
derby-4932-05-aa-addJDBC4.0versions.diff, derby-4932-05-ab-addJDBC4.0versions.diff
> I have found StringColumnVTI to be a very useful class for removing the drudgery of writing
a table function. I would like to move it to move it into the package with the other public
vti machinery and then expose it as part of Derby's public api.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message