X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D2DFD3A3F26 for ; Sat, 6 Nov 2004 22:54:26 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 96854-08 for ; Sat, 6 Nov 2004 22:54:15 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 2F1E73A3E7F for ; Sat, 6 Nov 2004 22:54:17 +0000 (GMT) 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 iA6MsEJ7099510 for ; Sat, 6 Nov 2004 22:54:14 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id iA6MrNXB099386 for pgsql-php@postgresql.org; Sat, 6 Nov 2004 22:53:23 GMT From: ljb X-Newsgroups: comp.databases.postgresql.interfaces.php Subject: Re: sql problem with php Date: Sat, 6 Nov 2004 22:53:23 +0000 (UTC) Organization: Hub.Org Networking Services Lines: 39 Message-ID: References: <200411051233.10080.ff@dr.ufu.br> <200411061037.49469.xzilla@users.sourceforge.net> X-Complaints-To: usenet@news.hub.org User-Agent: slrn/0.9.8.0 (Linux) To: pgsql-php@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS X-Spam-Level: X-Archive-Number: 200411/4 X-Sequence-Number: 2948 xzilla@users.sourceforge.net wrote: > On Friday 05 November 2004 20:40, ljb wrote: >> ff@dr.ufu.br wrote: >> > Hi, >> > >> > I am having a problem with a system I developed using php with >> > postgres. ... >> > >> > I am not able to get a error_number in pgsql errors, only the error >> > message. So when I used pgsql 7.3 a used the string "referential >> > integrity violation" to detect this error, but on version 7.4 of pgsql >> > this string was replaced with "violates foreign key constraint" . >> > Anyone has a definitive solution on this or the way is to wait and change >> > all my code on future releases of pgsql? >> >> Unfortunately this is a limitation of the PHP PostgreSQL extension. >> PostgreSQL provids access to error numbers (I think as of 7.4) >> through libpq PQerrorField(), but PHP doesn't give you access to this yet. >> > > Actually I believe you can get it: > http://us2.php.net/manual/en/function.pg-result-error.php > > though this will only work in pg74 or greater. No, I don't think PHP has this capability (get the value of an error message subfield). The pg_result_error() you refer to gives you the whole message, which makes it hard for a program to determine exactly what went wrong. On the documentation page you point to, somebody added a comment referencing his own patch. The patch adds a PHP function called pg_result_error_field(), which lets a script get at the individual PostgreSQL error message fields. This would be a nice addition to PHP, but I don't know if the patch was submitted or accepted. It isn't in the latest PHP 4 release, 4.3.9. As you point out, however, it won't help the original poster still dealing with PostgreSQL 7.3, which doesn't have this feature.