Ben-Nes Michael wrote:
MySQL state ( at least 2 years ago ) that you dont need transaction becouse
you can always cancel your inserts by initiatin deletes. all true if the
code is perfect (...)
Far from that - transactions mean that other clients outside the
transaction see a consistent state as if your transaction haven't
happened, and after you commit it they see a new consistent state as
if ALL of it happened, no intermediate states which can cause breakage.
(e.g. a record was added to some table and then another record which
depends on it is added to another table. Without transactions someone
might see the intermediate state and won't be able to tell if there
is a logical problem with the database's state or it just happened to
see a temporary state. Similar reasons why atomic commits make
Subversion better than CVS).
This is something you simply can't accomplish without transactions
unless you practically implement them in the application level.
BTW - just to make sure people don't miss on other alternatives -
there are also Berkeley DB and Firebird as good complete SQL opensource
database implementations.
--Amos
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
