Res: RE: [PHP-DB] apache/php/mysql - guarenteed DB transaction
| From: | Ricardo Oliveira | Date: | Thu, 01 Jan 1970 00:00:00 +0000 |
| Subject: | Res: RE: [PHP-DB] apache/php/mysql - guarenteed DB transaction | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-32798@lists.php.net to get a copy of this message | ||
You should use
set autocommit = 0;
start transaction ;
insert code;
delete code;
update code;
commit or rollback depending on the result;
To do all this I had to use InnoDB table types.
Sorry, my english is quite pour,
Best regards,
Ricardo
-------Mensagem original-------
De: whynotpizza
Data: 02/04/04 20:39:13
Para: 'Matt Matijevich'; php-db@gremlins.biz; php-db@lists.php.net
Assunto: RE: [PHP-DB] apache/php/mysql - guarenteed DB transaction
Thanks guys, this is great info.
One last thought,
Suppose I have several DB transactions that I want to treat as 1 logical
transaction that I need to complete guarenteed.
For instance, an INSERT to one table, and a DELETE to another, and an UPDATE
to a third. All need to complete once a user selects submit.
What's the best approach to this scenario?
Thanks in advance for the help,
David
-----Original Message-----
From: Matt Matijevich [mailto:matijevich@alliancetechnologies.net]
Sent: Wednesday, February 04, 2004 11:17 AM
To: php-db@gremlins.biz; php-db@lists.php.net
Subject: Re: [PHP-DB] apache/php/mysql - guarenteed DB transaction
<snip>
Actually whether the script runs through to completion depends on the
'ignore_user_abort' setting.
</snip>
wow, guess you learn something everyday.
wish I would have known about that when I wrote a php script with some
terrible (lots of joins, just poorly designed) queries that took down my
webserver :(
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php