[
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-04-aa-retireDemoVersion.diff
Attaching derby-4932-04-aa-retireDemoVersion.diff. This patch removes the demo
version of StringColumnVTI. I will run the regression tests.
Touches the following files:
----------
M java/engine/org/apache/derby/vti/StringColumnVTI.java
Add some accessors to expose column name information which some subclasses need.
----------
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/StringColumnVTI.java
Retire this class.
----------
M java/demo/vtis/java/org/apache/derbyDemo/vtis/core/XmlVTI.java
M
java/demo/vtis/java/org/apache/derbyDemo/vtis/example/DerbyJiraReportVTI.java
Use new accessors to look up column names.
----------
M java/demo/vtis/java/org/apache/derbyDemo/vtis/core/FlatFileVTI.java
Extend public version of StringColumnVTI.
----------
M
java/demo/vtis/java/org/apache/derbyDemo/vtis/example/ApacheServerLogVTI.java
Eliminate the need for a setWasNull() method.
> 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.
