From: Gerard Samuel <php-db@trini0.org>
To: Martin Marques <martin@bugs.unl.edu.ar>
To: php-db@lists.php.net
Cc: pgsql-php@postgresql.org
Subject: Re: [PHP-DB] pg_result_error()
Date: Fri, 12 Dec 2003 09:19:36 -0500
Message-ID: <200312120908.18042.php-db@trini0.org> (raw)
In-Reply-To: <200312120844.16882.martin@bugs.unl.edu.ar>
References: <200312112209.54516.php-db@trini0.org>
<200312120844.16882.martin@bugs.unl.edu.ar>
Im going to CC this to the PostgreSQL list also.
On Friday 12 December 2003 06:44 am, Martin Marques wrote:
> El Vie 12 Dic 2003 00:09, Gerard Samuel escribió:
> > What good is this function?
> > A quick example of the wall Im running into ->
> > $sql = 'INSERT INTO .....';
> > $result = pg_query($conn_id, $sql);
> > if ($result === false)
> > {
> > var_dump( pg_result_error( $result ) );
>
> I would use here this:
> die(pg_result_error( $result ));
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().
> > According to the manual, pg_result_error takes the result resource.
> > If that resource is boolean false for one reason or another, then
> > pg_result_error isn't useful.
> > Anyone has any other ideas, besides using
> > pg_last_error()?
>
> Did you try it?
Yes I've tried it. In my DB class, Im currently using both pg_result_error()
and pg_last_error(), with pg_last_error() being secondary (a fall back) to
pg_result_error().
Because according to the manual ->
http://us2.php.net/manual/en/function.pg-last-error.php
--quote--
Error messages may be overwritten by internal PostgreSQL(libpq) function
calls. It may not return appropriate error message, if multiple errors are
occured inside a PostgreSQL module function.
Use pg_result_error(), pg_result_status() and pg_connection_status() for
better error handling.
--quote--
So again, I beg the question.
What good is pg_result_error(), when you *must* feed it boolean false and it
returns an empty string??
[0]
<?php
$conn = pg_connect("dbname=foo user=bar password=pass");
$sql = 'SELECT * FROM flagss'; // flags was misspelled
$result = @pg_query($conn, $sql); // returns false
if ($result === false)
{
die( pg_result_error($result) ); // results in an empty page????
}
?>
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: php-db@trini0.org, martin@bugs.unl.edu.ar, php-db@lists.php.net
Subject: Re: [PHP-DB] pg_result_error()
In-Reply-To: <200312120908.18042.php-db@trini0.org>
References: <200312112209.54516.php-db@trini0.org> <200312120844.16882.martin@bugs.unl.edu.ar> <200312120908.18042.php-db@trini0.org>
* 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