[DERBY-5839] dblook run on toursdb fails on triggers with java.lang.StringIndexOutOfBoundsException in dblook.log

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.2.2, 10.10.1.1
• Component/s: Tools
• Labels: derby_backport_reject_10_8

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

• Issue & fix info: High Value Fix, Newcomer, Repro attached
• Bug behavior facts: Regression
• Assignee: Mamta A. Satoor
• Reporter: Katherine Marsden
• Created: 02/Jul/12 22:43
• Updated: 03/Sep/14 08:31
• Resolved: 07/Aug/12 19:41

Description

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