Hello all. I have encountered an really annoying problem in MySQL 3.23.49 on Win32. I am using InnoDB because I need transactions. I use autocommit off. I'll try best to describe the problem I have: I have two sessions to my DB. Session 1 inserts some data into a table, then commits. Session 2 should normally be able to see data inserted by session 1, since session 1 has committed. But it is not the case. The only way I manage to get session 2 to see data inserted at session 1 is by doing a commit. Is this what should happen?
Please correct me if I am wrong, but using the READ_COMMITTED transaction isolation level, I should be achieving what I want, right? I used the following syntax to ensure that the read_committed level (which is apparently default to Mysql) is enforced: set global transaction isolation level read_commited; I tried using MySQL v4 beta, but same thing happens. Thanks for any clarification on what I am doing wrong. --------------------------------------------------------------------- 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
