Benjamin Pflugmann wrote: >Hi. > >Well, a perfect example of misunderstanding due to lack of >information. I interpreted your former description in a way that your >applications simply hangs. > My apologies for the sparse information in the e-mail to which you originally replied. It was actually my second posting of the problem, and referred by date to the original posting (26/04/2002 11:31) which did contain more details.
>Had you quoted the error message you got (or even told that you got >one), it would have been more obvious that you meant a rollback due to >an locking issue. > I did quote the error in the original posting... >Well, this time I start asking, instead of guessing again: Which table >type (MyISAM/InnoDB/BDB) do you use? Do you intend to use transactions >or not? > Again, the table type is mentioned in the original posting. I am using BDB tables, and I am making use of transactions. I would have thought that the comment in the script describing how to create the "test" database -- "CREATE TABLE x (id INT) TYPE=BDB" -- would have given the game away there anyway... >A possible reason that you observe the rollback one time and not the >other could be that the mysql client sets auto-commit differently? > Both clients are instances of the same program running on the same machine, so I don't believe they are setting auto-commit differently. Repeating the exercise explicitly setting "auto-commit=0;" in each of them makes do difference either. Steve > >Bye, > > Benjamin. > > >On Mon, Apr 29, 2002 at 05:37:12PM +0100, [EMAIL PROTECTED] wrote: > >>Something (I don't know whether it is BerkeleyDB, MySQL or DBD::mysql) >>detects that deadlock has occurred and seems to rollback the transaction >>being performed by one client, so as to let the other client's >>transaction complete. >> >[...] > >>"DBD::mysql::st execute failed: Deadlock found when trying to get lock; >>Try restarting transaction at D:\Temp\deadlock.pl line 14." >> >[...] > >>>mysql test < file_with_inserts >>> >>>from two clients to see if you can reproduce the deadlock this way. >> >>I tried this and couldn't reproduce the deadlock. I'm not sure what the >>"mysql" program would do if it ran into deadlock (would it roll one >>client's transaction back and fail, rollback and retry, or hang >>indefinitely?), but anyway I started with an empty test database, asked >>each client to do 10,000 inserts and finished up with 20,000 rows, so it >>looks like they both completed. >> >>I guess that shows it's a DBD::mysql problem, which I did suspect since >>the DBD::ADO interface works. >> >>With this, it's probably worth me going back to the mysql-mysql-modules >>list. >> --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
