Hello Mark, thanks for your answer. In fact the mysql shell where I update the row is using AUTOCOMMIT=1. Even after I issue a COMMIT manually the changes are not seen by the application. What I dont understand is that the program doing a SELECT has to issue an COMMIT to have all data available. Maybe I cannot see through the transaction model at all, but as far as I can see all other connections should have the data available after the session that changes data issues a COMMIT command. But in fact that doesnt happen here. For what reason ever.
Any other ideas ? regards, Heri > InnoDB takes a consistent 'snapshot' at the beginning of every > transaction. This enables the 'I' in the infamous 'ACID' test...which is > isolation...Transacations don't 'see' the effects of other transactions > until after the others commit. InnoDB runs by default in an 'isolation > level' of 'REPEATABLE_READ', which means that the isolation a particular > transaction 'sees' remains in effect until that transaction itself has > committed. InnoDB accomplishes this through the 'snapshotting' model > mentioned above. > > See > > http://www.innodb.com/ibman.html#InnoDB_transaction_model > > for more detailed information, or consult any handy transaction > processing or database textbook ;) > > -Mark --------------------------------------------------------------------- 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
