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] Closed: (DERBY-4932) Move the StringColumnVTI to the public api
Date Fri, 10 Dec 2010 16:55:01 GMT

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

Rick Hillegas closed DERBY-4932.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 10.8.0.0

> 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
>             Fix For: 10.8.0.0
>
>         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, derby-4932-06-aa-packageProtection.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.


Mime
View raw message