X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3DCEAD1B47F for ; Wed, 7 Jan 2004 11:35:36 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 97373-10 for ; Wed, 7 Jan 2004 07:34:49 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 5523AD1B47D for ; Wed, 7 Jan 2004 07:34:46 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i07BYjU6005679 for ; Wed, 7 Jan 2004 11:34:45 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i07BF7Br095014 for pgsql-sql@postgresql.org; Wed, 7 Jan 2004 11:15:07 GMT From: brendanl@iname.com (Brendan LeFebvre) X-Newsgroups: comp.databases.postgresql.sql, comp.databases.postgresql.questions Subject: Different query results in psql and Perl DBI with Postgres 7.2.1 Date: 7 Jan 2004 03:14:40 -0800 Organization: http://groups.google.com Lines: 27 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-sql@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/55 X-Sequence-Number: 16448 I have a script that updates one record in a PostgreSQL 7.2.1 database through the Perl DBI. Here is the output from my log, which outputs the query sent to the DBI and the return value: --- Update query: UPDATE item SET status='SOLD' WHERE item_id=1129832 1 rows affected. Update query: UPDATE item SET status='STORE' WHERE item_id=1130081 0E0 rows affected. --- In both cases, the target record exists without question, and in the latter case, I receive the expected "UPDATE 1" when I execute the same query from within psql. Even more perplexing: the "0E0" occurs ONLY when setting status to 'STORE', and not 100% of the time. (though it happens far more often than not.) It seems to operate in stretches, too: when I am getting 1-row updates back from the latter query type, it happens several times in succession. Where do I even begin to attempt a diagnosis?