Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 30 Jul 2012 18:39:35 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1630124357.117236.1343673575107.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <612624829.188.1341269097911.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (DERBY-5839) dblook run on toursdb fails on
 triggers with java.lang.StringIndexOutOfBoundsException in dblook.log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425112#comment-13425112 ] 

Mamta A. Satoor commented on DERBY-5839:
----------------------------------------

I have been working on this issue and problem appears to be that starting 10.9, we have extended SYSTRIGGERS.REFERENCEDCOLUMNS to hold more information that it used to in prior releases. Prior to 10.9, REFERENCEDCOLUMNS held informatoin about the columns(optional). on which the trigger is defined. Starting 10.9, in addition to the columns info on which trigger is defined, we also hold information about the columns being used inside the trigger action plan. REFERENCEDCOLUMNS is an internal structure which users should not rely but dblook uses the information to construct trigger statements. I will debug more to see why the additional information in REFERENCEDCOLUMNS causing an issue with dblook in 10.9
                
> dblook run on toursdb fails on triggers with java.lang.StringIndexOutOfBoundsException in dblook.log
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5839
>                 URL: https://issues.apache.org/jira/browse/DERBY-5839
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.9.1.0
>         Environment: Not JVM/platform specific
> reproduced on Windows
> java version "1.7.0"
> Java(TM) SE Runtime Environment (build pwi3270-20110906_01)
> IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20110810_88604 (JIT enabled, AOT enabled)
> J9VM - R26_Java726_GA_20110810_1208_B88592
> JIT  - r11_20110810_20466
> GC   - R26_Java726_GA_20110810_1208_B88592
> J9CL - 20110810_88604)
> JCL - 20110809_01 based on Oracle 7b147
> Also seen on Mac with JDK 1.6
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>
> Running dblook on toursdb (either in packaged demo/databases/toursdb in the bin distribution or generated/toursdb after a build) fails to generate ddl for triggers and gives a java.lang.StringIndexOutOfBoundsException in the dblook.log.
> To reproduce:
> java org.apache.derby.tools.dblook -d 'jdbc:derby:toursdb'
> output shows:
> -- ----------------------------------------------
> -- Note: At least one unexpected error/warning message was
> -- DDL Statements for triggersration.  See dblook.log
> -- ----------------------------------------------
> dblook.log contains:
> java.lang.StringIndexOutOfBoundsException
>         at java.lang.String.substring(String.java:1131)
>         at org.apache.derby.tools.dblook.getColumnListFromDescription(dblook.java:664)
>         at org.apache.derby.impl.tools.dblook.DB_Trigger.createTrigger(DB_Trigger.java:130)
>         at org.apache.derby.impl.tools.dblook.DB_Trigger.doTriggers(DB_Trigger.java:82)
>         at org.apache.derby.tools.dblook.go(dblook.java:547)
>         at org.apache.derby.tools.dblook.<init>(dblook.java:142)
>         at org.apache.derby.tools.dblook.main(dblook.java:97)
> This seems to be a regression in 10.9. 10.8 works fine for me

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira