[
https://issues.apache.org/jira/browse/DERBY-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797777#action_12797777
]
Knut Anders Hatlen commented on DERBY-4504:
-------------------------------------------
Actually, the assert also detects an error that the non-debug builds don't
detect. This sequence of statements should fail, I think, because T.* is
ambiguous (could refer to S1.T or S2.T), but it doesn't fail with insane jars:
ij> create table s1.t(x int);
0 rows inserted/updated/deleted
ij> create table s2.t(x int);
0 rows inserted/updated/deleted
ij> select t.* from s1.t join s2.t on 1=1;
X |X
-----------------------
0 rows selected
The assert is triggered on debug builds, though:
ij> select t.* from s1.t join s2.t on 1=1;
ERROR XJ001: Java exception: 'ASSERT FAILED allTableName (T) expected to be
null: org.apache.derby.shared.common.sanity.AssertFailure'.
> ASSERT FAILED allTableName (T) expected to be null
> --------------------------------------------------
>
> Key: DERBY-4504
> URL: https://issues.apache.org/jira/browse/DERBY-4504
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.3.0, 10.6.0.0
> Reporter: Knut Anders Hatlen
>
> I see this assert failure in debug builds:
> ij> create table t(x int);
> 0 rows inserted/updated/deleted
> ij> select t.* from t join t on 1=1;
> ERROR XJ001: Java exception: 'ASSERT FAILED allTableName (T) expected to be
> null: org.apache.derby.shared.common.sanity.AssertFailure'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
