I want to know if concurrently UPDATE .... LIMIT N will not overlap with more than one client querying the db.
After UPDATE ... LIMIT N the client will make a SELECT with some client_id assigned. I don't want clients to overlap results, so every client will have different records each time the query the db with the SELECT after the update.
This depends on table engine?
The update locks the table/records? (I am sure this one depends on engine).
From my opinion UPDATE LIMIT should not overlap results, dbs have ACID property...I want to confirm this.