You may use option WITH LOCK IGNORE on client2 client2: select * from t1 WITH LOCK IGNORE
you can still set ISOLATION LEVEL to 1 or 10 to get only committed row, this will be select * from t1 WITH LOCK IGNORE ISOLATION LEVEL 1 "Tomas Simecek" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > > I have one question about locks. I have following code: > > client1: > begin tran > insert into t1 values (1, 2, 3) > > client2: > select * from t1 > > -- now this client2 is stopped until > client1: > commit/rollback > > > I tried different isolation levels on client1, but in all cases it was > the same. Isn't there any way that insert will not create exclusive lock > but shared or just hide the new created record to client2 so it can > proceed (like in oracle) until the end of transaction on client1 ? > > Thanks, > Tom > > > > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
