[
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-03-aa-useInMemoryDBinDemos.diff
Attaching derby-4932-03-aa-useInMemoryDBinDemos.diff. Before changing the demo
vtis to use the new StringColumnVTI, I thought it would be good to cleanup the
existing demo scripts. This patch makes the demo scripts use an in-memory
database. Committed at subversion revision 1043130.
Touches the following files:
M java/demo/vtis/sql/demoFileVtis.sql
M java/demo/vtis/sql/demoForeignDbmsVtis.sql
> 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
>
>
> 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.
