The documentation puts me off going with BDB tables - since there is a big performance
hit.
There is a fair bit in the manual as to the preferred approach under MySQL ie atomic
updates.
At the moment for MyISAM tables - the fast ones I understand - it seems that all we
have
to play with is Lock tables to
prevent other threads interfering with the data and that we can be confident that
inserts
will not be
compromised by another thread deleting or updating data inconsistent with the proposed
insert/update SQL. The
snag for me is that all obscure input from the user and every other eventuality has to
be
forseen and
trapped to avoid sending dud SQL to MySQL. We are potentially left then with some of
the
inserts/updates failing and not others going through - obviously unacceptable.
The TO DO list in version 3.22 talks about atomic inserts/updates which would solve
all my
problems ie they
all happen or all do NOT happen. If MySQL can do this then I don't care about
rollback. I
would dearly like to use the fast tables rather than compromise speed using DBD tables.
Be interested to know if atomic updates are a possibility under the latest version and
if
anyone has experience with them.
Phil Daintree
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
