From: Barry Lind <barry@xythos.com>
To: pgsql-sql@postgresql.org
Subject: Re: Something I'd like to try...
Date: Tue, 03 Oct 2000 10:38:50 -0700
Message-ID: <39DA19AA.9C87067A@xythos.com> (raw)
References: <200010030322.XAA05358@candle.pha.pa.us>
<16699.970547357@sss.pgh.pa.us>
It is interesting that this should come up now. Just last week I was
trying to port a SQL statement from Oracle to Postgresql that used table
aliases in an update statement. While I can see that this functionality
wouldn't be used very often it can be very useful under certain
circumstances.
I have a table that stores a hierarchy. Sometimes in an update I want
to join back to the same table to get other information related to
children or parent rows. In Oracle I can do this using the alias, but
in Postgresql I cannot.
Consider the SQL statements below as simplistic examples of what I was
doing in Oracle:
table_foo
foo_id int
parent_foo_id int
column_a int
column_b int
update table_foo f1
set column_a = (select sum(column_a) from table_foo f2
where f2.parent_foo_id = f1.foo_id);
update table_foo f1
set column_b = 1
where exists (select column_a from table_foo f2
where f2.parent_foo_id = f1.foo_id);
thanks,
--Barry
Tom Lane wrote:
>
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Can someone comment on this?
> >>
> >> I just noticed that postgres doesn't totally support
> >> column aliases on UPDATE statements, for example
>
> The SQL92 spec very clearly does not allow an alias on the target table:
>
> 13.10 <update statement: searched>
>
> <update statement: searched> ::=
> UPDATE <table name>
> SET <set clause list>
> [ WHERE <search condition> ]
>
> While I'm willing to consider variations from the spec that add
> significant functionality, this proposed addition adds no functionality
> worth noticing. It'd just be another way to trip yourself up when
> moving across DBMSes.
>
> regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: barry@xythos.com
Subject: Re: Something I'd like to try...
In-Reply-To: <39DA19AA.9C87067A@xythos.com>
References: <200010030322.XAA05358@candle.pha.pa.us> <16699.970547357@sss.pgh.pa.us> <39DA19AA.9C87067A@xythos.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox