At 11:38 27/08/00 -0400, Tom Lane wrote:
>Philip Warner <pjw@rhyme.com.au> writes:
>>> SELECT ... FROM (a cross join b) cross join c
>> I'm not sure whether the above is the syntax you plan to use, but it looks
>> a little too much like:
>> SELECT ... FROM (select * from a cross join b) as z cross join c
>> which has a quite different meaning to any kind of outer join,
>
>Huh? AFAIK they mean exactly the same thing, modulo a few issues about
>visibility of columns. In any case you'll have to take your complaint
>to ISO, because that's what the spec says the syntaxes are.
Sorry, I should have written:
SELECT ... FROM (select * from a,b) as z, c
which does not do an outer join, and does not imply any ordering.
>> I don;t think that support for this kind of query is implemented,
>
>Not yet, but it's certainly on the TODO list. I'm not seriously
>thinking about getting subselect-in-FROM done in this go-round,
>though.
Great! If by Subselect-in-from you mean something like what I wrote above,
then it is a major win.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/