[
https://issues.apache.org/jira/browse/DERBY-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782448#action_12782448
]
Knut Anders Hatlen commented on DERBY-4451:
-------------------------------------------
The patch looks good to me. I tried something similar in DERBY-4448 (see
comment dated 19/Nov/09 08:12 AM) but for some reason that I don't remember
now, I also made some changes to when
InsertNode.enhanceAndCheckForAutoincrement() was called. This caused a failure
in GeneratedColumnsTest. I'm trying to remember why I thought that change was
needed in addition to removing the call to forbidGenerationOverrides(), but
nothing comes to mind, so I'm guessing I just wasn't thinking clearly at that
moment. +1 to commit if the regression tests ran cleanly.
> ArrayIndexOutOfBoundsException or ASSERT FAILED when inserting generated
> columns out of order
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-4451
> URL: https://issues.apache.org/jira/browse/DERBY-4451
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.3.0, 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dag H. Wanvik
> Attachments: derby-4451.diff, derby-4451.stat, derby-4451b.diff,
> derby-4451b.stat, derby-4451c.diff, derby-4451c.stat, derby-4451d.diff,
> derby-4451d.stat
>
>
> I see this error when I specify the columns in a different order than in the
> table definition. It only fails if a multi-row table constructor is used.
> ij> create table t(a int, b generated always as (-a));
> 0 rows inserted/updated/deleted
> ij> insert into t(b,a) values (default,1);
> 1 row inserted/updated/deleted
> ij> insert into t(b,a) values (default,1), (default, 2);
> ERROR XJ001: Java exception: '1 >= 1:
> java.lang.ArrayIndexOutOfBoundsException'.
> And in a sane build:
> ij> insert into t(b,a) values (default,1),(default,2);
> ERROR XJ001: Java exception: 'ASSERT FAILED More columns in result column
> list than in base table: org.apache.derby.shared.common.sanity.AssertFailure'.
> This bug may be similar to DERBY-4448, but the stack trace is different, and
> DERBY-4448 does not raise an ASSERT FAILED in sane builds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
