db-derby-dev mailing list archives

[jira] Commented: (DERBY-4932) Move the StringColumnVTI to the public api

Date

Wed, 08 Dec 2010 00:46:05 GMT

[ https://issues.apache.org/jira/browse/DERBY-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969100#action_12969100
]
Rick Hillegas commented on DERBY-4932:
--------------------------------------
Tests passed cleanly for me except for the ping test. Committed derby-4932-04-aa-retireDemoVersion.diff
at subversion revision 1043245.
> 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
>
>
> 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.