Re: MySQL transactions
| From: | Manuel Lemos | Date: | Wed, 05 Jul 2000 23:18:53 +0000 |
| Subject: | Re: MySQL transactions | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-23647@lists.php.net to get a copy of this message | ||
Hello Kristian,
On 05-Jul-00 10:23:29, you wrote:
>Manuel Lemos wrote:
>> There are some requirements regarding to which types tables MySQL supports
>> transactions.
>The tables must be created as TYPE=BDB. These tables will not
Isn't that enough to configure build MySQL with --with-berkeley-db ?
That's what I did.
>use the native MySQL tables, but go through the Sleepycat DB3
>support instead. It is highly unlikely that MySQL will have
>transactions on TYPE=ISAM, TYPE=MYISAM or TYPE=HEAP tables ever.
I'm not sure about the impact of what you are saying, but a robust business
application requires a database that supports transactions, especially if
money is envolved. It's not admissable to deal with somebody's money while
risking to get the values in the database be inconsistent or corrupted by failed
transactions that could not be rolled back.
So, whatever takes to make MySQL support transactions is worthy the alleged
performance penalty. After all, most (if not all) of the serious databases
support transactions and so MySQL as to support transactions to be taken
seriously. The same goes for sub-queries that MySQL misses among other SQL-92
inconformances.
Regards,
Manuel Lemos
Web Programming Components using PHP Classes.
Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org
--
E-mail: mlemos@acm.org
URL: http://www.mlemos.e-na.net/
PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp
--