Re: Not so good transaction support
> 1. Please explain the above in detail. It depends on the type of table you're using. If you're using a table type that only supports table-level locking, then each transaction is isolated by being suspended until the previous transaction is done. This is slower if you do a lot of longer transactions but quite safe. > I think the only difference is functions(COMMIT, ROLLBACK) support. This is true, for some table types -- for others, you'll find things work as you expected -- see InnoDB or that other table type (Gemini :-). -- Michael T. Babcock http://www.fibrespeed.net/~mbabcock/ - 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
Re: Not so good transaction support
What you are trying to perform is doable with InnoDB table handler. Unlike BDB, InnoDB has multi-versioning and consistent reads. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com - 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
