Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 23 Jun 2011 09:30:47 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2070952575.32756.1308821447461.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <656981165.8397.1308171167533.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5280) Large batch of DDL in a database
 procedure dies on a transaction severity error.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-5280:
--------------------------------------

    Attachment: d5280.diff

All regression tests ran cleanly with DERBY-5161 backed out. Committed to trunk with revision 1138787.

> 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
>            Assignee: Knut Anders Hatlen
>         Attachments: d5280.diff, junit-repro.diff
>
>
> 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