Re: Add Missing From?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add Missing From?
Date: 2004-08-10 17:16:58
Message-ID: 29527.1092158218@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> * Allow an alias to be provided for the target table in UPDATE/DELETE
>>
>> This is not SQL-spec but many DBMSs allow it.

> I don't think we would ever do the above item.

Why not? You can hardly argue that "it's not SQL spec" while
simultaneously putting in a much larger extension to the spec.

> I see no purpose to
> allowing the UPDATE/DELETE table to have an alias

Brevity. If you are really updating AVeryLongSchemaName.AVeryLongTableName
then you would reasonably want to have an alias for that. In the pure
SQL-spec syntax it's not so important because there's seldom a need to
name the table again within the query. But in a self-join situation you
would be forced to name the target table within the query, and then a
shorter alias would be both easier to type and less prone to confusion.
(Even in pure SQL, you may need to name the table again for references
within subqueries that have duplicate column names.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-08-10 17:23:20 Re: Add Missing From?
Previous Message Bruce Momjian 2004-08-10 17:09:09 Re: Add Missing From?