You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2006/12/16 00:25:22 UTC
[jira] Commented: (DERBY-2152) Support diagnostic vti tables that
take parameters, such as SpaceTable
[ http://issues.apache.org/jira/browse/DERBY-2152?page=comments#action_12458972 ]
Daniel John Debrunner commented on DERBY-2152:
----------------------------------------------
Is there any reason to make SYSCS_DIAG part of the syntax, much more flexible for it to be a standard schema name that is passed into the bind code and then onto the data dictionary?
> Support diagnostic vti tables that take parameters, such as SpaceTable
> ----------------------------------------------------------------------
>
> Key: DERBY-2152
> URL: http://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_testing_v1.patch, d2152_v1.stat
>
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira