[
https://issues.apache.org/jira/browse/DERBY-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463333
]
A B commented on DERBY-2152:
----------------------------
I haven't heard anything regarding the latest patch for this issue
(d2152_vtiMappingCleanup_v1.patch), so I'm inclined to commit it. If anyone is
planning to review, please let me know; otherwise I'll go ahead and commit it
tomorrow (Wednesday) PST.
> Support diagnostic vti tables that take parameters, such as SpaceTable
> ----------------------------------------------------------------------
>
> Key: DERBY-2152
> URL: https://issues.apache.org/jira/browse/DERBY-2152
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Daniel John Debrunner
> Assigned To: A B
> Attachments: d2152_engine_v1.patch, d2152_engine_v2.patch,
> d2152_junit_jdk16_fix.patch, d2152_testing_v1.patch, d2152_testing_v2.patch,
> d2152_v1.stat, d2152_v2.stat, d2152_vtiMappingCleanup_v1.patch,
> d2152_vtiMappingCleanup_v1.stat, junit-errors.txt
>
>
> Expand the work of DERBY-571 to support the remaining diagnostic tables that
> take parameters.
> Syntax would use the table constructor, like (not sure if an 'AS' clause will
> be required:
> select * from TABLE(SYSCS_DIAG.SPACE_TABLE(?, ?))
> Diagnostic VTIs that could be handled this way are:
> ErrorLogReader(String log file name)
> SpaceTable(String tableName)
> SpaceTable(String schemaName, String tableName)
> StatementDuration(String inputFileName)
> This is the second stage mentioned in DERBY-571
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
