On Thursday 12 December 2002 11:23, Horst Scheruga wrote: > If I use the transaction isolation level of READ-COMMITTED, > I have the problems that I do not see changes to the table made > within another connection (and commited) until I call commit in my > connection. > > As of my understanding this behaviour is correct for the REPEATABLE-READ > and SERIALIZABLE isolation level, but not for READ-COMMITTED. > > Beside the fact that this is not the behaviour I expect, > this results in performance loss, because lots of version have to be > created if multiple users have open connections. > > I tried this under Windows 2000 [Version 5.00.2195] SP 3. > (The variables and status are attached to this mail)
[skip] > version 4.0.4-beta-max-nt [skip] READ COMMITTED is supported only since 4.0.5 -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ 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
