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: Sample files -- BadQuery w/Errnum patch part 4

Subject: Re: Sample files -- BadQuery w/Errnum patch part 4

2007-10-25       - By Warren Young

 Back
Jim Wallace wrote:
> +   deadlock1 and deadlock2: Tests detecting a deadlock between
> +            two transactions, using the BadQuery::what_errnum() value

I've looked at these, and have some concerns:

1. The database creation stuff belongs in resetdb.

2. Why does the first example need the loop?  The second pass isn't
actually needed to make it deadlock, is it?

3. If the new tables are created and populated ahead of time by resetdb,
it seems to me that the two programs are so close to each other that it
should be possible to have just one program, which you run twice.  I
don't quite understand the nature of the deadlock, but maybe if you just
add second cin.getline() call between the two SELECT queries, so the
first is sitting and waiting halfway through when you start the second?

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