List:MySQL++« Previous MessageNext Message »
From:Jim Wallace Date:October 25 2007 2:52pm
Subject:RE: Expose errnum() in query -- BadQuery w/Errnum patch part 3
View as plain text  
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@stripped] 
> 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=1
> 
> 
> 
Thread
RELEASE: v2.3.2Warren Young11 Jul
  • Getting errnum() in exception?Jim Wallace20 Sep
    • Re: Getting errnum() in exception?Warren Young22 Sep
  • Building the head of SVN with MSVC?Jim Wallace25 Sep
    • Re: Building the head of SVN with MSVC?Warren Young26 Sep
  • Error num in BadQuery patchJim Wallace25 Sep
    • RE: Error num in BadQuery patchJim Wallace26 Sep
      • Re: Error num in BadQuery patchWarren Young26 Sep
    • Re: Error num in BadQuery patchWarren Young26 Sep
  • v2.3.2 and execute?Jim Wallace5 Oct
    • Re: v2.3.2 and execute?Warren Young5 Oct
  • Building svn tip on WindowsJim Wallace24 Oct
    • Re: Building svn tip on WindowsWarren Young25 Oct
  • Patch for better exception use -- BadQuery w/Errnum patch part 1Jim Wallace24 Oct
  • Better exception usage -- BadQuery w/Errnum patch part 2Jim Wallace24 Oct
  • Expose errnum() in query -- BadQuery w/Errnum patch part 3Jim Wallace24 Oct
    • Re: Expose errnum() in query -- BadQuery w/Errnum patch part 3Warren Young25 Oct
      • RE: Expose errnum() in query -- BadQuery w/Errnum patch part 3Jim Wallace25 Oct
  • BadQuery w/Errnum patch part 4Jim Wallace24 Oct
    • Re: BadQuery w/Errnum patch part 4Warren Young25 Oct
      • RE: BadQuery w/Errnum patch part 4Jim Wallace25 Oct
  • Sample files -- BadQuery w/Errnum patch part 4Jim Wallace24 Oct
    • Re: Sample files -- BadQuery w/Errnum patch part 4Warren Young25 Oct
      • RE: Sample files -- BadQuery w/Errnum patch part 4Jim Wallace25 Oct
        • Re: Sample files -- BadQuery w/Errnum patch part 4Warren Young25 Oct
          • RE: Sample files -- BadQuery w/Errnum patch part 4Jim Wallace25 Oct
          • RE: Sample files -- BadQuery w/Errnum patch part 4Jim Wallace25 Oct
            • Re: Sample files -- BadQuery w/Errnum patch part 4Warren Young25 Oct
              • RE: Sample files -- BadQuery w/Errnum patch part 4Jim Wallace25 Oct
      • RE: Sample files -- BadQuery w/Errnum patch part 4Jim Wallace25 Oct