Hi! Job Miller wrote in message <[EMAIL PROTECTED]>... >yes, thank you though. >not in MyISAM tables, which is what mine are, and >again according the manual, you slow things down >significantly for transaction support.
Transactional InnoDB tables are actually faster in many simple benchmarks than MyISAM. Set innodb_flush_log_at_trx_commit=0 to avoid disk write at each commit. See benchmarks at http://www.innodb.com/bench.html >is it worth it? instead of my previously suggested >method of handling it? or is there something better? Regards, Heikki Innobase Oy >--- CC Zona <[EMAIL PROTECTED]> wrote: >> In article >> ><[EMAIL PROTECTED]>, >> [EMAIL PROTECTED] (Job Miller) wrote: >> >> > without save points and rollback what is the best >> way >> > to replace all records for a user that might have >> been >> > edited with their new values. >> >> To clarify: are you aware that MySQL does have >> transaction support >> available, or is using it not an option for you >> here? >> >> -- >> CC >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, e-mail: >> [EMAIL PROTECTED] >> For additional commands, e-mail: >> [EMAIL PROTECTED] >> To contact the list administrators, e-mail: >> [EMAIL PROTECTED] >> > > >__________________________________________________ >Do You Yahoo!? >Make a great connection at Yahoo! Personals. >http://personals.yahoo.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
