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] Updated: (DERBY-4401) Document USING clause in joins
Date Mon, 26 Apr 2010 07:59:31 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen updated DERBY-4401:

    Attachment: using.zip

Here's a first stab at documentation for the USING clause. I added a new topic for it and
pointed to it from the syntax descriptions for INNER JOIN, LEFT OUTER JOIN and RIGHT OUTER

I'll commit the patch shortly, so that at least some documentation for the USING clause makes
it into the release candidate that's planned later today. Post-commit suggestions for improvements
are welcome, though.

> Document USING clause in joins
> ------------------------------
>                 Key: DERBY-4401
>                 URL: https://issues.apache.org/jira/browse/DERBY-4401
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: using.diff, using.zip
> DERBY-4370 made some of the join operations accept a USING clause. This should be documented
in the reference manual.
> The JOIN operations section talks about "join clause", which should be fine since that
could mean both ON clause and USING clause.
> The sections INNER JOIN operation, LEFT OUTER JOIN operation and RIGHT OUTER JOIN operation
need to be updated with the new syntax. We need to replace
> {
>     ON booleanExpression
> }
> with
> {
>     { ON booleanExpression } |
>     { USING ( Simple-column-Name [ , Simple-column-Name ]* ) }
> }
> Perhaps it would make sense to factor out this part of the syntax into a separate element
JoinSpecification, and explain the meaning of USING there.

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

View raw message