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: Error num in BadQuery patch

Subject: Re: Error num in BadQuery patch

2007-09-26       - By Warren Young

 Back
Jim Wallace wrote:
> Some of you may have thought this was pretty bogus.

Some of us maintainers were skeptical, yes. :)

> However, what I thought was causing mysql_errno to be cleared was
> incorrect.  I thought the only API called after the error was
> mysql_error. Instead it is a successful rollback in ~Transaction that
> sets mysql_errno to zero.  

Thanks for chasing it down, and posting about it.  I'd have had to
duplicate the work you've done to assure myself that it was useful
before I could even think of accepting the patch.  And there's a good
chance I wouldn't have bothered, so I'd have just rejected your patch
entirely instead of just nit-picking it mercilessly. :)

> Here's the test case

Not necessary in this case, since it's obvious from the explanation why
Connection::errnum() wasn't working for you.  No need to do any more
work than necessary.

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