----- Original Message -----
From: Steve Leibel <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 23, 2001 3:54 PM
Subject: $DBI::err values?
> How do I get a list of the error codes returned via $DBI::err for
> Mysql? I can't find anything in the Mysql docs, and strangely enough
> I couldn't get this question answered on the Mysql mailing list
> either. Thanks for any pointers.
>
Quoted from the DBI documentation...
You might wanna use DBI::errstr() intead, because it gives textual messages
WARNING AND ERROR MESSAGES
Fatal Errors
Can't call method ``prepare'' without a package or object reference
The $dbh handle you're using to call prepare is probably undefined because
the preceding connect failed. You should always check the return status of
DBI methods, or use the RaiseError attribute.
Can't call method ``execute'' without a package or object reference
The $sth handle you're using to call execute is probably undefined because
the preceeding prepare failed. You should always check the return status of
DBI methods, or use the RaiseError attribute.
DBI/DBD internal version mismatch
The DBD driver module was built with a different version of DBI than the one
currently being used. You should rebuild the DBD module under the current
version of DBI.
(Some rare platforms require ``static linking''. On those platforms, there
may be an old DBI or DBD driver version actually embedded in the Perl
executable being used.)
DBD driver has not implemented the AutoCommit attribute
The DBD driver implementation is incomplete. Consult the author.
Can't [sg]et %s->{%s}: unrecognised attribute
You attempted to set or get an unknown attribute of a handle. Make sure you
have spelled the attribute name correctly; case is significant (e.g.,
``Autocommit'' is not the same as ``AutoCommit'').
Warnings
Database handle destroyed without explicit disconnect
A $dbh handle went out of scope or the program ended before the handle was
disconnected from the database. You should always explicitly call disconnect
when you are finished using a database handle. If using transactions then
you should also explicitly call commit or rollback before disconnect.
DBI Handle cleared whilst still holding %d cached kids!
Most probably due to a DBI bug. Possibly a DBD driver bug. Please report it.
DBI Handle cleared whilst still active!
Most probably due to a DBI bug. Possibly a DBD driver bug. Please report it.
DBI Handle has uncleared implementors data
Most probably a DBD driver bug. Please report it.
DBI Handle has %d uncleared child handles
Most probably due to a DBI bug. Possibly a DBD driver bug. Please report it.
----------------------------------------------------------------------------
----
