From: Josh Berkus <josh@agliodbs.com>
To: John B. Scalia <jscalia@cityblueprinting.com>
To: pgsql-sql@postgresql.org
Subject: Re: Bug in psql - Postgresql 7.3.1?
Date: Fri, 3 Oct 2003 12:45:07 -0700
Message-ID: <200310031245.08177.josh@agliodbs.com> (raw)
In-Reply-To: <001a01c389b0$e00773a0$2501a8c0@John>
References: <001a01c389b0$e00773a0$2501a8c0@John>
John,
>
> UPDATE my_table SET field1='new_value' AND SET field2='different_value'
> WHERE my_table_id = 'key';
Well, your SQL is bad:
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.
> 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
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.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, jscalia@cityblueprinting.com
Subject: Re: Bug in psql - Postgresql 7.3.1?
In-Reply-To: <200310031245.08177.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox