Re: Minimize locking on UPDATE with multiple WHERE columns
Posted by:
Rick James
Date: March 23, 2013 12:23AM
After a client has grabbed 100 rows, what does it do? Does it proceed to do 100 SQL statements? In that case, it might be 'better' to grab only one row at a time.
Do they need to grab 100 consecutive items? Is it ok if they grab less than 100?
Did you try it with the index I suggested?
Could you provide SHOW CREATE TABLE.
Subject
Views
Written By
Posted
1766
March 17, 2013 09:07AM
1061
March 21, 2013 09:28AM
989
March 21, 2013 02:34PM
Re: Minimize locking on UPDATE with multiple WHERE columns
920
March 23, 2013 12:23AM
943
March 25, 2013 08:13AM
973
March 28, 2013 12:04AM
1003
April 05, 2013 01:38PM
917
April 05, 2013 07:05PM
965
April 05, 2013 07:32PM
987
April 05, 2013 10:16PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.