From: | "Tarabas" <tarabas(at)tarabas(dot)de> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Strange Update-Bug in postgres (is it a feature?) ?! |
Date: | 2002-04-15 17:02:16 |
Message-ID: | IEEEIIEOMKMOKHPPJGJIMEJJDOAA.tarabas@tarabas.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi!
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 ...
On MS-SQL both work fine ... since I use finals for the tablefields in my
java-program to build the queries/updates from, it's kinda bad if I remove
the table in front of the field (because they could be used in updates as
well as joined-selects where i would need them!) ... So it would be great if
both versions would work as they do on other DB-Systems ... why is that
different ... does that serve a certain purpose ?!
Any chance to change that behaviour ?!
Regards ... Manuel ...
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Tkach | 2002-04-15 17:07:20 | Alter/update large tables - VERRRY annoying behaviour! |
Previous Message | Andrew Sullivan | 2002-04-15 16:57:37 | Re: Why does postgres not take into account my index on a bigint column ? |