[
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-02-ab-moveStringColumnVTI.diff
Attaching derby-4932-02-ab-moveStringColumnVTI.diff. The first rev of this
patch passed derbyall. However, the JUnit tests bombed at the outset on an
InvocationTargetException raised because StringColumnVTI wasn't included in the
engine jar. This second rev of the patch adds StringColumnVTI to the engine
jar. I am re-running the JUnit tests.
This patch touches the following additional file:
-----------
M tools/jar/extraDBMSclasses.properties
Adds StringColumnVTI to the list of extra classes which need to be included in
the engine jar.
> 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
>
>
> 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.
