# [PATCH] Ingres error reporting functions

- Thread: https://externals.io/message/16034
- Original archive: https://news-web.php.net/php.internals/16034
- Started by Croker on 2005-04-19T15:02:32+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #16034 — Croker — 2005-04-19T15:02:32+00:00

URL: https://externals.io/message/16034#16034

Ok, 

As you say there does not seem to be any consistent naming of functions.
A fact I guess PDO will address. I have changed the names to match mysql
and have a 3rd function (ingres_errsqlstate) that reports the SQLSTATE
of the last statement run. With Ingres SQLSTATE and errno is not the
same thing since errno is more granular than SQLSTATE.

The revised code can be found in this link:

http://www.ingres.co.uk/php/head/ingres_error_reporting_rev2.diff

thanks

grant

> -----Original Message-----
> From: Lukas Smith [mailto:lsmith@php.net]
> Sent: 19 April 2005 16:25
> To: Croker, Grant
> Cc: internals@lists.php.net
> Subject: Re: [PATCH] Ingres error reporting functions
> 
> Grant Croker wrote:
> 
> > […]
the
> > […]
error
> > […]
under
> > […]
> 
> I know its too late to fix this in the current database extensions
(who
> all follow either the native, the mysql ext or some random naming the
> given developer came up with), but you might want to atleast try and
> follow an existing database extension with the function naming. I
guess
> ext/mysql or mysqli might be a good rolemodel just because its used
alot.
> 
> regards,
> Lukas