Re: Bug in psql - Postgresql 7.3.1?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: "John B(dot) Scalia" <jscalia(at)cityblueprinting(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Bug in psql - Postgresql 7.3.1?
Date: 2003-10-03 19:47:16
Message-ID: 20031003194716.GB23110@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Fri, Oct 03, 2003 at 09:18:44 -0400,
"John B. Scalia" <jscalia(at)cityblueprinting(dot)com> wrote:
> All,
>
>
>
> I'm not certain if what I'm trying to do is legal, but if I execute a
> statement like:
>
>
>
> UPDATE my_table SET field1='new_value' AND SET field2='different_value'
> WHERE my_table_id = 'key';

It should be:
UPDATE my_table SET field1='new_value', field2='different_value'
WHERE my_table_id = 'key';

> in psql, it reports that it has successfully updated one record.

I am not sure why you aren't getting a syntax error.

> However, the record does not appear to be updated when I subsequently
> issue a SELECT for that record. I'll buy the fact that I may be using
> illegal syntax - I'm not SQL expert, but the update says it worked when
> in fact it did not. Should this have worked or should it have reported
> an error?

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Josh Berkus 2003-10-03 20:16:10 Re: Bug in psql - Postgresql 7.3.1?
Previous Message Josh Berkus 2003-10-03 19:45:07 Re: Bug in psql - Postgresql 7.3.1?