From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Tarabas <tarabas(at)tarabas(dot)de> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Strange Update-Bug in postgres (is it a feature?) ?! |
Date: | 2002-04-15 18:12:52 |
Message-ID: | 20020415110202.C31537-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 15 Apr 2002, Tarabas wrote:
> Is this a bug or a feature:
>
> When I try an update like this
> "update mail set mail.mailread=1 where mail.mail_id=123" I get the Error
> "Error while executing query parse error near '.'"
>
> Then I try
>
> "update mail set mailread=1 where mail.mail_id=123" and it works fine ...
I believe this is what the SQL92 standard asks for. It seems to want
<column name> = <update source> rather than something like
<column reference> = <update source>
My memory is rather flaky but I vaguely remember a recent discussion on
something similar (maybe column names in insert lists?) that made it sound
like it might be possible to convince a change, but it would probably have
to properly error on cases where the names didn't match properly.
From | Date | Subject | |
---|---|---|---|
Next Message | mike | 2002-04-15 18:14:32 | Re: Scaling postgres |
Previous Message | Michael Loftis | 2002-04-15 18:03:48 | Re: Why does postgres not take into account my index on a bigint column ? |