Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <882965770.1251927992757.JavaMail.jira@brutus>
Date: Wed, 2 Sep 2009 14:46:32 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4355) Implement CROSS JOIN
In-Reply-To: <1929921730.1250585834780.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen updated DERBY-4355:
--------------------------------------

    Attachment: cross.diff

Here's an untested patch that adds support for CROSS JOIN in the parser, and that seems to be enough to get it working.

ij> create table t1(x int);
0 rows inserted/updated/deleted
ij> insert into t1 values 1,2;
2 rows inserted/updated/deleted
ij> create table t2(x char(1));
0 rows inserted/updated/deleted
ij> insert into t2 values 'a','b';
2 rows inserted/updated/deleted
ij> select * from t1 cross join t2;
X          |X   
----------------
1          |a   
1          |b   
2          |a   
2          |b   

4 rows selected

> Implement CROSS JOIN
> --------------------
>
>                 Key: DERBY-4355
>                 URL: https://issues.apache.org/jira/browse/DERBY-4355
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>         Environment: any
>            Reporter: Bernt M. Johnsen
>         Attachments: cross.diff
>
>
> Implement the CROSS JOIN syntax
> SELECT * from t1 CROSS JOIN t2;
> as an alternative syntax to
> SELECT * FROM t1, t2; 
> This should be pretty straight forward and ease the migration of SQL code to Derby.

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