db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Synge (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2152) Support diagnostic vti tables that take parameters, such as SpaceTable
Date Mon, 18 Dec 2006 19:26:24 GMT
    [ http://issues.apache.org/jira/browse/DERBY-2152?page=comments#action_12459435 ] 
James Synge commented on DERBY-2152:

How interesting (i.e. convenient for me :-) ) that you're working on this at the same
time that I'm working on DERBY-47 (IN optimization).  I'm experimenting with
transforming a query such as:

SELECT * FROM tableA WHERE columnB IN (constC, ?, ?, constD)


SELECT * FROM tableA WHERE columnB IN (SELECT vti.column1 FROM new ArgsToRowsVTI(SomeArgs))

An issue I've not yet resolved is when/how to pass the arguments to the ArgsToRowsVTI instance.
It needs to have one column with the same type as columnB (known at compile/bind time).
And it needs to have N rows (4 in the example above), with the values in the original IN list
(including parameter markers).

I'm interested in any thoughts regarding when and how to pass the arguments.  For example,
I could
imagine that InListOperatorNode.preprocess will return a SubqueryNode, such that the original
query show above would become:

SELECT * FROM tableA WHERE columnB IN (SELECT vti.column1 FROM new ArgsToRowsVTI(typeOfColumnB,
constC, ?, ?, constD))

Any thoughts/advice?

> 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


View raw message