X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A0011D1B4B7 for ; Fri, 12 Dec 2003 21:52:20 +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 00431-04 for ; Fri, 12 Dec 2003 17:51:51 -0400 (AST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by svr1.postgresql.org (Postfix) with ESMTP id 54F4FD1B482 for ; Fri, 12 Dec 2003 17:51:48 -0400 (AST) Received: from hivemind.trini0.org (trini0.org[68.39.114.118]) by comcast.net (sccrmhc11) with ESMTP id <2003121221514901100ldq8de>; Fri, 12 Dec 2003 21:51:49 +0000 Received: from gladiator.trini0.org (gladiator.trini0.org [192.168.0.3]) by hivemind.trini0.org (Postfix) with ESMTP id 9C7889A; Fri, 12 Dec 2003 16:51:49 -0500 (EST) From: Gerard Samuel To: Martin Marques , php-db@lists.php.net Subject: Re: [PHP-DB] pg_result_error() Date: Fri, 12 Dec 2003 16:51:49 -0500 User-Agent: KMail/1.5.4 Cc: pgsql-php@postgresql.org References: <200312112209.54516.php-db@trini0.org> <200312120908.18042.php-db@trini0.org> <200312121224.57200.martin@bugs.unl.edu.ar> In-Reply-To: <200312121224.57200.martin@bugs.unl.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312121651.49375.php-db@trini0.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/24 X-Sequence-Number: 2470 On Friday 12 December 2003 10:24 am, Martin Marques wrote: > > That is fine and all, but my original example was just an example of the > > non functionality of pg_result_error(), not how to handle errors when a > > query fails. > > But for arguement sake, lets use your example in some dummy code[0]. > > $result is still boolean false, and pg_result_error() will still return > > an empty string, and using die, would just die, with no report of what > > happened. Then whats the use of pg_result_error(). > > Looks like you are totally right. Tried it and it works horrible. Any idea > on why this is like this? > Seems like Im not the only one who thought this function is useless... http://bugs.php.net/bug.php?id=18747 So Im going to modify my code to not use this function, as it is really a total waste of time at the moment. Thanks for the chat...