William Lewis Brown wrote:
> I have the ability, in the application I am writing, to fix-up errors in a
> mysql database on the fly. For example, if a select from a table fails because
> the table does not exist, I can create the table. I know this sounds a bit
> strange, but in the context of my application, it works out just fine.
> I have not found in any DBI documentation a full list of the error codes
> the MySQL driver can spit back to the user via $h->err. I would much rather use
> this error code than parse errstr, even if these codes are database specific.
> So, does anyone have a full list of the mysql error codes?
> Should I be processing errors differently?
The driver returns just the error codes from libmysqlclient. So all you
have to do is checking the MySQL docs.
|• $h->err error codes||William Lewis Brown||31 Oct|
| • Re: $h->err error codes||Jochen Wiedmann||6 Nov|