[ http://issues.apache.org/jira/browse/DERBY-1204?page=all ]
Bryan Pendleton resolved DERBY-1204.
------------------------------------
Fix Version/s: 10.2.2.0
10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks for providing the 10.2 patch. My build and test runs were clean, and I
committed the change to the 10.2 branch as revision 482484.
> CREATE TRIGGER with an INSERT action statement with multiple rows and a
> referenced column throws a StringIndexOutOfBoundsException
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1204
> URL: http://issues.apache.org/jira/browse/DERBY-1204
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.1.2.1, 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Yip Ng
> Fix For: 10.2.2.0, 10.3.0.0
>
> Attachments: derby1204-10.2-diff01.txt, derby1204-10.2-stat01.txt,
> derby1204-trunk-diff01.txt, derby1204-trunk-diff02.txt,
> derby1204-trunk-stat01.txt, derby1204-trunk-stat02.txt
>
>
> These triggers succeed
> create trigger tgood after insert on x
> for each statement mode db2sql insert into x values (666), (999), (333);
> create trigger tgood after insert on x
> referencing new as n
> for each row mode db2sql insert into x values (n.x);
> create trigger tgood after insert on x
> referencing new as n
> for each row mode db2sql insert into x values (333), (999), (333)
> This one fails
> create trigger tgood after insert on x
> referencing new as n
> for each row mode db2sql insert into x values (n.x), (999), (333);
> Test cases will be added to triggerGeneral under this bug number.
> java.lang.StringIndexOutOfBoundsException: String index out of range: -3
> at java.lang.String.substring(String.java:1444)
> at
> org.apache.derby.impl.sql.compile.CreateTriggerNode.bindReferencesClause(CreateTriggerNode.java:421)
> at
> org.apache.derby.impl.sql.compile.CreateTriggerNode.bind(CreateTriggerNode.java:258)
> at
> org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:344)
> at
> org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:118)
> at
> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:713)
> at
> org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:560)
> at
> org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:507)
> at org.apache.derby.impl.tools.ij.ij.executeImmediate(ij.java:313)
> at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:433)
> at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:310)
> at org.apache.derby.impl.tools.ij.Main.go(Main.java:203)
> at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:169)
> at org.apache.derby.impl.tools.ij.Main14.main(Main14.java:55)
> at org.apache.derby.tools.ij.main(ij.java:60)
--
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
