On Tue, 2006-10-31 at 10:35 -0600, Dan Nelson wrote: > In the last episode (Oct 31), Ow Mun Heng said: > > Just wanted to post this here to see if anyone knows the difference. > > > > In MSSQL, there is a hint which can be used to ask the DB to not lock > > the tables during queries and then to read un-commited/dirty data. > > This command is like > > > > select count(*) from MyTable nolock > > > > in MySQL, I found that I can do the same thing with the same syntax. > > Having read through this post in the forum, > > http://forums.mysql.com/read.php?60,81970,82201#msg-82201 > > > > I'm just curious to know if anyone knows that they are one and the same. > > I don't see anything in that thread indicating that MySQL supports a > "nolock" keyword. The 2nd post says to run a
Sorry it was another post somewhere http://bloggingabout.net/blogs/ramon/archive/2006/09/29/Change-the-isolation-leven-to-read-uncommitted-data-in-MSSQL.aspx and after playing around with it, seems that the information is incorrect. Sorry for the noise. > set transaction isolation level READ UNCOMMITTED; > > statement before your query, which will put your session in a state > similar to MSSQL's nolock mode. I understand that innodb don't need these locking hints (as it uses mvcc) but I'm looking for ways to have the same queries run in bot mssql and mysql with the minimum of changes in the SQL query. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
