Properly allowing concurrent UPDATEs in MySQL???
Posted: Sat Mar 14, 2009 10:21 pm
Hi all,
I have search the forum but haven't found a post that addressed my questions.
I have a client that has requested a database that will keep track of a small private school. Their requirements are fairly simple for the most part: keeping track of student attendance and keeping track of various miscellaneous notes on each student.
The only thing that is worrying me at this time is that the database will need to be accessed concurrently by many users. So I see the situation where the same record will be accessed at the same time and the subsequent issues with updating that particular row at the same time: for example when both user open the same unedited row and then proceed to modify it at different times causing one user to overwrite the previous update's changes.
What kind of implementations would you recommend that would help combat these scenarios. I was thinking of implementing last update timestamps and while this would be sufficient in a site of such requirements I am curious as to how to have a more solid application.
Sorry for the long post, if I haven't elaborated properly I will gladly expand further.
Thanks in advance everyone
Frank
I have search the forum but haven't found a post that addressed my questions.
I have a client that has requested a database that will keep track of a small private school. Their requirements are fairly simple for the most part: keeping track of student attendance and keeping track of various miscellaneous notes on each student.
The only thing that is worrying me at this time is that the database will need to be accessed concurrently by many users. So I see the situation where the same record will be accessed at the same time and the subsequent issues with updating that particular row at the same time: for example when both user open the same unedited row and then proceed to modify it at different times causing one user to overwrite the previous update's changes.
What kind of implementations would you recommend that would help combat these scenarios. I was thinking of implementing last update timestamps and while this would be sufficient in a site of such requirements I am curious as to how to have a more solid application.
Sorry for the long post, if I haven't elaborated properly I will gladly expand further.
Thanks in advance everyone
Frank