Re: native error handling in PEAR::DB drivers
| From: | Jon Parise | Date: | Mon, 09 Jun 2003 15:48:30 +0000 |
| Subject: | Re: native error handling in PEAR::DB drivers | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17204@lists.php.net to get a copy of this message | ||
On Mon, Jun 09, 2003 at 01:12:53PM +0200, Roman Neuhauser wrote:
> these are the bases of errorNative() methods of individual drivers:
>
> DB/fbsql.php : fbsql_errno()
> DB/ibase.php : -
> DB/ifx.php : ifx_error() . ' ' . ifx_errormsg()
> DB/msql.php : -
> DB/mssql.php : -
> DB/mysql.php : mysql_errno()
> DB/mysql4.php : mysql_errno()
> DB/oci8.php : OCIError()['code']
> DB/odbc.php : odbc_error() . ' ' . odbc_errormsg()
> DB/pgsql.php : pg_errormessage()
> DB/sybase.php : sybase_get_last_message()
>
> shouldnn't they all behave the same, returning either the number or the
> text? I'd like to push some of the code up to the parent (DB::common),
> but these trivial differences make it problematic.
I think the lowest common denominator is going to be the error code,
and it makes sense that all of the errorNative() calls should return a
consistent type of error.
Perhaps errorNative() could grow an optional parameter ($verbose?)
that would indicate that the caller was also interested in the error
text (if available), as well?
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)