db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yip Ng (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1960) Handle null compilation schema to improve statement cache mechanism
Date Sun, 15 Oct 2006 18:27:34 GMT
Handle null compilation schema to improve statement cache mechanism

                 Key: DERBY-1960
                 URL: http://issues.apache.org/jira/browse/DERBY-1960
             Project: Derby
          Issue Type: Improvement
          Components: SQL
    Affects Versions:
         Environment: Any
            Reporter: Yip Ng

A compilation schema with null value indicates that the trigger action statement text does
not depend on the current schema. This means:

1. It is safe to compile this statement in any schema since there is no dependency with
    the CURRENT SCHEMA. i.e.: All relevent fields are qualified with a specific schema.

2. The statement cache mechanism can utilize this piece of information to enable
    better statement plan sharing across different schemas; thus, avoiding unnecessary
    statement compilation. 

This is a follow-up work of DERBY-630.  To improve the statement cache mechanism, the system
needs to handle the null compilation schema in statement preparation logic.  It may require
some work on the SQL parser to determine whether the compiled statement depends on the CURRENT
SCHEMA or not, so that the compilation schema can be properly set. 

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