X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id E5B77D1B508 for ; Fri, 3 Oct 2003 13:19:32 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 48392-02 for ; Fri, 3 Oct 2003 10:18:46 -0300 (ADT) Received: from chimta05.algx.net (mta6.algx.net [67.92.168.235]) by svr1.postgresql.org (Postfix) with ESMTP id B2E0ED1B506 for ; Fri, 3 Oct 2003 10:18:42 -0300 (ADT) Received: from John (ip216-203-212-194.z212-203-216.customer.algx.net [216.203.212.194]) by chimmx05.algx.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HM600JHUNN9VK@chimmx05.algx.net> for pgsql-sql@postgresql.org; Fri, 03 Oct 2003 08:18:46 -0500 (CDT) Date: Fri, 03 Oct 2003 09:18:44 -0400 From: "John B. Scalia" Subject: Bug in psql - Postgresql 7.3.1? To: pgsql-sql@postgresql.org Message-id: <001a01c389b0$e00773a0$2501a8c0@John> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook, Build 10.0.4024 Content-type: multipart/alternative; boundary="Boundary_(ID_GPvWkl3PNtmCGVQBWMcQtQ)" Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=HTML_50_60 X-Spam-Level: X-Archive-Number: 200310/53 X-Sequence-Number: 15453 This is a multi-part message in MIME format. --Boundary_(ID_GPvWkl3PNtmCGVQBWMcQtQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT 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'; 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? 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. TIA, John --Boundary_(ID_GPvWkl3PNtmCGVQBWMcQtQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

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’;

 

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?

 

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.

 

TIA,

John

--Boundary_(ID_GPvWkl3PNtmCGVQBWMcQtQ)--