Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: "John B. Scalia" <jscalia@cityblueprinting.com>, pgsql-sql@postgresql.org
Subject: Re: Bug in psql - Postgresql 7.3.1?
Date: Fri, 3 Oct 2003 12:45:07 -0700
User-Agent: KMail/1.4.3
References: <001a01c389b0$e00773a0$2501a8c0@John>
In-Reply-To: <001a01c389b0$e00773a0$2501a8c0@John>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200310031245.08177.josh@agliodbs.com>

John,

>=20
> UPDATE my_table SET field1=3D'new_value' AND SET field2=3D'different_valu=
e'
> WHERE my_table_id =3D 'key';

Well, your SQL is bad:

UPDATE my_table SET field1=3D'new_value, field2=3D'different_value'
WHERE my_table_id =3D 'key';

> in psql, it reports that it has successfully updated one record.
> 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?

It's an error if it actually occurred that way.  Can you cut-and-paste your=
=20
actual PSQL session?

> For record, this is Postgresql 7.3.1 on Solaris 9. Problem originally
> seen during a php4 script, but has been duplicated on the psql command
> line.

BTW, there are known bugs in 7.3.1; you should upgrade to 7.3.4.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco