db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4370) Implement JOIN ... USING syntax
Date Tue, 08 Sep 2009 15:59:57 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752589#action_12752589

Knut Anders Hatlen commented on DERBY-4370:

Thanks for digging into the standard, Dag. I agree that what you quoted above must mean that
the behaviour seen with the patch is in accordance with the standard. It's strange, though,
that both PostgreSQL and MySQL have interpreted this in another way. Does anyone have access
to other DBMSs where they could test this query and see which columns they return?

> Implement JOIN ... USING syntax
> -------------------------------
>                 Key: DERBY-4370
>                 URL: https://issues.apache.org/jira/browse/DERBY-4370
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: using.diff
> The SQL standard defines two ways to specify the join condition in an INNER JOIN or a
(LEFT/RIGHT/FULL) OUTER JOIN: with an ON clause or with a USING clause. Derby currently only
accepts joins with an ON clause. Internally, Derby has code that supports USING. This code
should be enabled to ease the migration to Derby. We must also verify that the implementation
adheres to the standard before we enable it.
> Since USING is already a reserved keyword in Derby's parser, enabling the USING syntax
should not cause any compatibility issues for existing queries.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message