Dude... if you use LOCK TABLE WRITE (not READ) on the table.. it will STAY
locked.. until you give the UNLOCK command. It completely solves any
concurrency issues. This is a fundamental database issue and MySQL is
meant to handle it. :)
-Mike
At 05:19 PM 4/25/02 -0400, Matt Babineau wrote:
thread1 > updates and increments a numebr in the DB
thread2 > does the same thing as thread one
thread1 > reads the database to get the new value for display on the
web page
thread2 > also reads the database for the new updated value.
so thread1 displays "2" and thread2 display
