[ http://issues.apache.org/jira/browse/DERBY-2152?page=comments#action_12458975 ] Daniel John Debrunner commented on DERBY-2152: ----------------------------------------------
On issue 1 I would say that the no-argument lock table should not be supported as a TABLE(function). I guess I'd thought about having separate resolution for the two different types, tables that map to vtis and table functions that map to vtis. I think with the way you have combined it this select will kind of be accepted (at least the name will be bound) SELECT * FROM SYSCS_DIAG.SPACE_TABLE but I think this should fail with a table not found exception. >From looking at the patch I now see that the SYSCS_DIAG is not part of the >syntax grammar, but matches the existing use for the diagnostic tables. > 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
