AS operator and subselect result names: PostgreSQL vs. Oracle - Mailing list pgsql-general

From nzanella@cs.mun.ca (Neil Zanella)
Subject AS operator and subselect result names: PostgreSQL vs. Oracle
Date
Msg-id b68d2f19.0310312044.3c98da8d@posting.google.com
Whole thread Raw
Responses Re: AS operator and subselect result names: PostgreSQL  (Peter Eisentraut <peter_e@gmx.net>)
Re: AS operator and subselect result names: PostgreSQL  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Re: AS operator and subselect result names: PostgreSQL vs. Oracle  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hello,

I would like to ask the about the following...

PostgreSQL allows tables resulting from subselects to be renamed with
an optional AS keyword whereas Oracle 9 will report an error whenever
a table is renamed with the AS keyword. Furthermore, in PostgreSQL
when the result of a subselect is referenced in an outer select
it is required that the subselect result be named, whereas this
is not true in Oracle. I wonder what standard SQL has to say
about these two issues. In particular:

1. Does standard SQL allow an optional AS keyword for (re/)naming
   tables including those resulting from subselects.

and

2 Why must a subselect whose fields are referenced in an outer query
  be explicitly named in PostgreSQL when it is not necessary in Oracle.

Thanks,

Neil

pgsql-general by date:

Previous
From: Ryan Mack
Date:
Subject: PostgreSQL License Question
Next
From: Lynn.Tilby@asu.edu
Date:
Subject: Re: 7.3.5 release (was: Re: SELECT with row>32k hangs over