MySQL Bugs: #8347: transaction php apache

Bug #8347	transaction php apache
Submitted:	6 Feb 2005 23:47	Modified:	7 Feb 2005 8:40
Reporter:	Dick Stins	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	all	OS:	Linux (linux redhat)
Assigned to:		CPU Architecture:	Any

Description:
I need to have full control over transactions. 

When I do have an open transaction, then I should be able to continue it at the next http request (now it will be rolled back when the script ends and the transaction is still open).

The easiest method is to have an unique database connection id or transaction id which can be used to tell mysql that it should the unfinished transaction of the previous script.
...
...
....
...
Now does apache and php have no control over it.
See also: http://forums.mysql.com/read.php?22,13554,13554#msg-13554

How to repeat:
This is very critical. It keeps serious applications like webERP from full control of  database transactions while  this is really needed to compete with serious ERP products.

Suggested fix:
The easiest method is to have an unique database connection id or transaction id which can be reused to tell mysql that it should continue with the unfinished transaction of the previous script.
...
...
....
...

this is actually a feature request. Could you please to set appropriate 'severity'?

Well that's pretty interesting. Mysql is great for internet. Mysql (innodb) supports transactions. Php is excellent to combine with mysql. Apache too.

But all together is the support for database transactions almost zero. 

It's too easy to tell everybody that this is technically not a bug.......

When it is not a bug, then it needs to be documented:
tell everybody that apache + php + mysql is a bad combination for implementing database transactions........