Hello mysql,
I'm planing to use transactions in application written in PHP, which
of course uses pconnect to optimize perfomance.
Few time ago I had to stop using "lock tables" as this lead to
locked system then somehow the php script was aborted before unlock
tables.
With transactions we could have the same bad situation if it's not
handeled, it's even worse as the result is unexpected depending on
the following statements transaction can be committed or rolled back.
I'm speaking about the following problem:
I issue the begin statement and some of the statements, then PHP
script is aborted before the transaction is committed, but as
connection is not terminated mysql does not rolls it back. The next
statements come from the other PHP script so they could commit
transaction or roll it back.
The question is - does this problem present or not ? If it does I
think it would be nice to modify the behavior so PHP would unlock
all the tables and rollback all the transactions from the previous
script.
--
Best regards,
Peter mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
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
