network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 1 month |
| seen | Mar 31 '12 at 21:39 | |
| stats | profile views | 1 |
|
May 13 |
awarded | Notable Question |
|
Jan 11 |
awarded | Popular Question |
|
Mar 31 |
awarded | Scholar |
|
Mar 31 |
accepted | InnoDB row locking - how to implement |
|
Mar 31 |
comment |
InnoDB row locking - how to implement Aaron; yes that is what I am trying to do. I've looked at using something like gearman - but that was a bust. You have something else in mind? |
|
Mar 30 |
comment |
InnoDB row locking - how to implement Thanks. It doesn't seem to solve my issue, when two threads are coming in with "SELECT id FROM items WHERE status='pending' LIMIT 1 FOR UPDATE;" and they both see the same row, then one will lock the other. I was hoping somehow it would be able to by-pass the locked row and goto the next item which was pending.. |
|
Mar 30 |
awarded | Student |
|
Mar 30 |
comment |
InnoDB row locking - how to implement thanks for the answer. As I have this table and 100 clients checking for pending items I was getting a lot of collisions - 2-3 clients getting the same pending row. Table lock is to slow. |
|
Mar 30 |
asked | InnoDB row locking - how to implement |
