Thanks a lot Philippe. Its working. :) sujay
-----Original Message----- From: Philippe Poelvoorde [mailto:[EMAIL PROTECTED] Sent: Friday, August 19, 2005 12:43 PM To: 'mysql@lists.mysql.com ' Subject: Re: Commit needed even after a select statement ?? HI, n(say session 2) and updated the entries in the table. Did a > commit. > * Now i issued the second select statement on session 1, but still it > is showing the old results. Idealy it should show the new results, > which are a result of updations done using session 2. > > But when i issue a commit after the first select on session 1, and do > the rest as i mentioned above, it is showing all the results properly. > Is this the intended behaviour or do i need to make any configuration > changes or any ?? I guess you are using the default behaviour which is : 'Repeatable-read' http://dev.mysql.com/doc/mysql/en/innodb-transaction-isolation.html try 'read uncommited', or just drop the transaction since what you are observing is perfectly normal... -- Philippe Poelvoorde COS Trading Ltd. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
