[
https://issues.apache.org/jira/browse/DERBY-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759151#action_12759151
]
Knut Anders Hatlen commented on DERBY-4380:
-------------------------------------------
Thanks for taking the time to check the standard, Mamta! My understanding is
the same as yours. Basically, it looks like the standard allows the same
syntactic elements in ON clauses as in WHERE clauses:
<join condition> ::= ON <search condition>
<where clause> ::= WHERE <search condition>
> SOME not allowed in ON clause
> -----------------------------
>
> Key: DERBY-4380
> URL: https://issues.apache.org/jira/browse/DERBY-4380
> Project: Derby
> Issue Type: Bug
> Components: Store
> Reporter: Bernt M. Johnsen
> Attachments: on_subquery.diff
>
>
> SOME is not allowed in ON-clause:
> ij> create table t1 (i integer);
> 0 rows inserted/updated/deleted
> ij> create table t2 (i integer);
> 0 rows inserted/updated/deleted
> ij> create table t3 (i integer);
> 0 rows inserted/updated/deleted
> ij> insert into t1 values (1);
> 1 row inserted/updated/deleted
> ij> insert into t2 values (2);
> 1 row inserted/updated/deleted
> ij> insert into t3 values 2,3,4;
> 3 rows inserted/updated/deleted
> ij> select * from t1 where t1.i = some (select i from t3);
> I
> -----------
> 0 rows selected
> ij> select * from t1 inner join t2 on t1.i = some (select i from t3);
> ERROR 42972: An ON clause associated with a JOIN operator is not valid.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
