db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yip Ng (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2183) Trigger recompilation problem when trigger action has its table not qualified with a schema
Date Sun, 17 Dec 2006 02:25:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2183?page=all ]

Yip Ng updated DERBY-2183:

    Attachment: derby2813-trunk-stat01.txt

Attaching initial patch derby2813-trunk-diff01.txt for review.  derbyall and junit test suite
passes successfully.  

The problem was that the compilation schema for the SPS was never set during its recompilation,
it was using the current schema to perform the recompilation which is not correct.  It should
have use the SPS's compilation schema to do the recompilation when we push the compiler context.

On a side note, I think I might have found/encountered another problem with trigger while
I was fixing this bug.  Specifically in the area of trigger execution context(TEC) in the
LCC.  For instance, when a trigger reaches its maximum recursion allowed, it appears that
the TEC count is not being reset properly, causing the maximum recursion to be thrown again
for a statement that merely triggers no more than two TECs. I'll file a separate jira for
this issue.

> Trigger recompilation problem when trigger action has its table not qualified with a
> -------------------------------------------------------------------------------------------
>                 Key: DERBY-2183
>                 URL: http://issues.apache.org/jira/browse/DERBY-2183
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,
>         Environment: Any
>            Reporter: Yip Ng
>         Assigned To: Yip Ng
>         Attachments: derby2813-trunk-diff01.txt, derby2813-trunk-stat01.txt
> Trigger recompilation problem when trigger action has its table not qualified with a
> SPSs in SYS.SYSSTATEMENTS get invalidated for recompilation when sqlj.install_jar, sqlj.remove_jar,
sqlj.replace_jar are called, or when a database upgrade is performed.  The problem arises
when the trigger action statement does not qualify the table with an explicit schema name.
 During recompilation it uses the default schema instead of using the original schema that
was persisted in SYS.SYSSTATEMENTS causing an exception to occur.  e.g.:
> C:\derby\trunk>java -classpath classes;. org.apache.derby.tools.ij
> ij version 10.3
> ij> connect 'jdbc:derby:wombat;create=true';
> ij> create table app.t1 (i int, j int);
> 0 rows inserted/updated/deleted
> ij> insert into app.t1 values (1,10);
> 1 row inserted/updated/deleted
> -- notice trigger action's update statement did not qualify table t1 with a schema name
> ij> create trigger app.tr1 after update of i on app.t1 update t1 set j = 1;
> 0 rows inserted/updated/deleted
> ij> update app.t1 set i=i+1;
> 1 row inserted/updated/deleted
> ij> select * from app.t1;
> I          |J
> -----------------------
> 2          |1
> 1 row selected
> -- this action invalidates the SPS and mark for recompilation
> ij> call sqlj.install_jar('c:/derby/procs/Procs.jar', 'APP.Procs', 0);
> 0 rows inserted/updated/deleted
> ij> disconnect;
> ij> connect 'jdbc:derby:wombat' user 'user1';
> -- recompilation occurs but uses 'USER1' as the schema to compile instead of 'APP', resulting
in error
> ij> update app.t1 set i=i+1;
> ERROR 42Y07: Schema 'USER1' does not exist
> ij>

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