[
https://issues.apache.org/jira/browse/DERBY-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6256:
---------------------------------
Attachment: derby-6256-06-aa-revampVTIdemos.diff
Attaching derby-6256-06-aa-revampVTIdemos.diff. This patch modernizes the code
in derbyDemo/vtis.
At this point, much of the code prototyped by the VTI demos has moved into the
product. XmlVTI is now part of the public api and the foreignViews optional
tool provides a standard way to view a foreign database.
This patch makes the following changes:
1) Eliminates the early version of XmlVTI which appeared in the VTI demos.
References to XmlVTI now point at the version in the public api.
2) Eliminates the support classes and script for viewing a MySQL database. That
support is now provided by the documented foreignViews optional tool.
3) Simplifies the README file.
Touches the following files:
M java/demo/vtis/sql/demoFileVtis.sql
D java/demo/vtis/sql/demoForeignDbmsVtis.sql
D java/demo/vtis/java/org/apache/derbyDemo/vtis/snapshot
D java/demo/vtis/java/org/apache/derbyDemo/vtis/snapshot/Subscription.java
D
java/demo/vtis/java/org/apache/derbyDemo/vtis/snapshot/SnapshotQuery.java
D
java/demo/vtis/java/org/apache/derbyDemo/vtis/snapshot/SubscriptionSignature.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTIHelper.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/XmlVTI.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/QueryVTIHelper.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/XMLRow.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/QueryRow.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/core/VTITemplate.java
D java/demo/vtis/java/org/apache/derbyDemo/vtis/example/VTIs.java
M
java/demo/vtis/java/org/apache/derbyDemo/vtis/example/DerbyJiraReportVTI.java
M
java/demo/vtis/java/org/apache/derbyDemo/vtis/example/ApacheServerLogVTI.java
D
java/demo/vtis/java/org/apache/derbyDemo/vtis/example/WorldDBSnapshot.java
M java/demo/vtis/README
> Move the XmlVTI into the product.
> ---------------------------------
>
> Key: DERBY-6256
> URL: https://issues.apache.org/jira/browse/DERBY-6256
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Tools
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Labels: derby_triage10_11
> Attachments: derby-6256-01-aa-move-XmlVTI-into-product.diff,
> derby-6256-02-aa-allowParentTags.diff, derby-6256-03-aa-useFileNotURL.diff,
> derby-6256-04-aa-addURLFactoryMethodAndTests.diff,
> derby-6256-05-aa-javadocTypo.diff, derby-6256-06-aa-revampVTIdemos.diff
>
>
> The XmlVTI under derbyDemo has been useful to me for many years. It has
> become even more useful now that Derby supports varargs. That is because
> varargs make it very easy to declare an XmlVTI. At this point, I think it is
> worth re-phrasing the XmlVTI in terms of varargs and moving it into the
> product so that we can use it for internal table functions. There is no rush
> to expose XmlVTI as part of Derby's public api, but we could consider doing
> that if other people find this table function to be useful.
> The XmlVTI is a table function which turns an xml file into a tabular data
> set which you can query via sql. When you declare an XmlVTI, you state the
> following arguments:
> 1) The url of an xml file.
> 2) The name of the element in the xml file which you want to treat as a
> record or row.
> 3) The names of the attributes and subelements of that record which you want
> to treat as columns. Now that we have varargs, it is possible to represent
> this trailing argument as a variable length argument list.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
