Re: MySQL transactions
| From: | Kristian Köhntopp | Date: | Thu, 06 Jul 2000 11:05:16 +0000 |
| Subject: | Re: MySQL transactions | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-23694@lists.php.net to get a copy of this message | ||
Manuel Lemos wrote:
> >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.
No, that is not enough. Only when the table type is set to BDB,
the berkely db code is being used to manage the tables. For
all other table types, the appropriate native code from the
MySQL people is being used and this code still does not know
anything about transactions and it is likely that it will never
know about them, ever.
> >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.
You can get very far with MySQL without transactions, but for
some operations transactions are necessary. They are also slow.
Which is why MySQL gives you the choice, through the specification
of the table type, which is more important to you.
> 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.
I have seen some financial software (for example early versions
of the Cybercash Cash Register) from the inside, and transactions
are not going to save them, either. 1/2 :-) CCR may have improved
over time - I do not know current versions at all - but what I
received back then (Version 2, in beta) was a chest of screws
and parts (how do you translate "Eine Kiste Schrauben" into
an appropriate english expressions). It was by no means a
product, transactions or not. An overall design robustness
is much more important than individual features of subproducts
such an transactions in a database.
Kristian
--
Kristian Köhntopp, NetUSE AG Siemenswall, D-24107 Kiel
Tel: +49 431 386 436 00, Fax: +49 431 386 435 99
Using PHP3? See our web development library at http://phplib.netuse.de/