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
El Vie 12 Dic 2003 11:19, Gerard Samuel escribió:
> 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 in
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(
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:
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 ) );
}
According to the manual, pg_result_error takes the result resource.
If that resource is
