Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• Subject: mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Subject: Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• Subject: MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Subject: Re: Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
Subject: RE: Expose errnum() in query -- BadQuery w/Errnum patch part 3

Subject: RE: Expose errnum() in query -- BadQuery w/Errnum patch part 3

2007-10-25       - By Jim Wallace

 Back
That's correct, you can't reproduce the problem unless there's a sql
call between the exception and your call to errnum(), which occurs on
the rollback of a transaction.  If you run the deadlock tests, it
demonstrates it.

> -- --Original Message-- --
> From: Warren Young [mailto:mysqlpp@(protected)]
> Sent: Thursday, October 25, 2007 9:16 AM
> To: MySQL++ Mailing List
> Subject: Re: Expose errnum() in query -- BadQuery w/Errnum
> patch part 3
>
> Jim Wallace wrote:
> > +   /// If you want the string *and* number you must
> > +   /// call errnum() before calling error() since error() clears
>
> I tried to replicate that by causing an error in one of the
> examples, then calling Connection::errnum(), then error(),
> then errnum() again, and it shows the same number both times.
>
> I think this is just leftover confusion from your initial
> problem diagnosis process.  It's not mysql_error() clearing
> the error number, it's the second error caused by the
> transaction failure.
>
> --
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe:
> http://lists.mysql.com/plusplus?unsub=jwallace@(protected)
>
>
>

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:    http://lists.mysql.com/plusplus?unsub=mysql@(protected)