How to UPDATE the same mysql row from multiple scripts at the same time?

The database type doesn't matter. MySQL is designed to automatically queue the asynchronous requests and execute them in the order in which they arrive. However, the requests will probably not even be asynchronous, unless you have a lot of them running at once.

Either way, you shouldn't have a problem with this, unless your scripts have to update the row in a specific order. In that case, you should use a single script where you can more closely control the updating order.

(I just have to add a column+1 to a row column so no order needed, but I do have to read the column value) – jarkam Sep 11 '10 at 20:56 1 Exactly. That's the beauty of MySQL, and most database systems for that matter. You don't have to worry about deadlocks or race conditions.

If you are just incrementing a field, you have nothing to worry about. – SimpleCoder Sep 11 '10 at 20:59 1 If, across 100 different scripts, you increment the same field at the same (or nearly the same) time, you can be sure that the final value of the field will be 100 more than what it was (after all 100 statements have executed, of course.) – SimpleCoder Sep 11 '10 at 21:01 1 Just tested opening 200 "threads" (php scripts) with a 100x loop updating the same row without sleeps and I got 20000 as final value on the row, looks like it works fine, I thought I was going to get errors from trying to update the same row, thanks for clarifying it for me. – jarkam Sep 11 '10 at 21:33 1 It's all part and parcel of RDBMS's "ACID": en.wikipedia.

Org/wiki/ACID – Marc B Sep 11 '107 at 3:58.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.