Chris skrev:
It doesn't explicitly say anything about when a connection is lost but
I'm guessing it would rollback the transaction (well I'd sure hope so).
Me too. In any case, I'm now also using register_shutdown_function,
which calls a function that does rollback of not committed
Reason I'm asking is, I've seen some deadlock issues in a script (using
FOR UPDATE and LOCK IN SHARE MODE), that looks like they are caused by
transactions not being rolled back (releasing locks) correctly.
Do you use pconnect? If I right remember there was a bug in some version
of mysql that
Chris skrev:
It should be rolled back when a connection is lost or a transaction
isn't explicitly committed.
Can you find documentation on this specific issue anywhere?
I think the same as you, but I find it odd, it is not documented.
Reason I'm asking is, I've seen some deadlock issues in a
Martin Koch Andersen wrote:
Chris skrev:
It should be rolled back when a connection is lost or a transaction
isn't explicitly committed.
Can you find documentation on this specific issue anywhere?
I think the same as you, but I find it odd, it is not documented.
Reason I'm asking is, I've
Hi,
In case the PHP script dies (from fatal error, die() or similar), is any
started transaction (BEGIN TRANSACTION) automatically rolled back
(ROLLBACK) by PHP then?
I can't find any documentation about this.
Thanks in advance for hints, links etc.
--
Martin - http://925.dk
Shoot for the
Martin Koch Andersen wrote:
Hi,
In case the PHP script dies (from fatal error, die() or similar), is any
started transaction (BEGIN TRANSACTION) automatically rolled back
(ROLLBACK) by PHP then?
It should be rolled back when a connection is lost or a transaction
isn't explicitly committed.
