db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5280) Large batch of DDL in a database procedure dies on a transaction severity error.
Date Wed, 15 Jun 2011 20:52:47 GMT
Large batch of DDL in a database procedure dies on a transaction severity error.
--------------------------------------------------------------------------------

                 Key: DERBY-5280
                 URL: https://issues.apache.org/jira/browse/DERBY-5280
             Project: Derby
          Issue Type: Bug
          Components: SQL
    Affects Versions: 10.8.1.2, 10.9.0.0
            Reporter: Rick Hillegas


The batch of DDL run by the procedure which registers database metadata functions now dies
with the following error:

ERROR 40XC0: Dead statement. This may be caused by catching a transaction severity error inside
this statement.

A process of binary search shows that this problem was introduced by revision 1086920 as part
of the work on DERBY-5161.

The bug can be reproduced by compiling the DBMDWrapper class attached to DERBY-3973 and then
running the following script:

connect 'jdbc:derby:memory:db;create=true'; 

create procedure registerPublicStaticMethods( in connectionURL varchar( 200 ), in printSQL
boolean )
language java parameter style java modifies sql data
external name 'DBMDWrapper.registerPublicStaticMethods';

call registerPublicStaticMethods( 'jdbc:default:connection', false );

If you change the second argument to registerPublicStaticMethods to true, then you will see
all of the DDL being issued by the database procedure. The procedure runs fine in 10.7 but
fails with this error in 10.8.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message