Re: aliasing table name in update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Holger Klawitter <holger(at)klawitter(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: aliasing table name in update
Date: 2001-04-13 17:20:31
Message-ID: 4807.987182431@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Holger Klawitter <holger(at)klawitter(dot)de> writes:
> Upgrading from 7.0.3 to 7.1(rc4) went very smooth - but a small
> issue came up:

> The following statement does not work any more:
> update l set i=2 from longname l where l.i=1;

I'd say it's a fluke that that ever was accepted. Given the obvious
ambiguity of interpretation (suppose there is a table named l?), it
should be rejected IMHO.

There has been some talk of allowing

update longname [as] l set ...

but we do not currently accept that.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-04-13 19:54:46 Re: Numeric modulo operator is incorrect.
Previous Message Tom Lane 2001-04-13 16:11:31 Re: backend crashes with mnogosearch