2

I have created an office scheduling program that uses jQuery to post to a PHP file which then inserts an appointment into a pgSQL database. This has not happened yet but I can foresee this problem in the future--two office workers try to schedule an appointment in the same slot at the same time, creating a race condition and one set of customer data would be lost, or at least I'd have to dig it out of a log. I was wondering if there was a flag I could set in the database, if I need to create some kind of gatekeeper program to control server connections, or if there is some kind of mutex/lock/semaphore I can use with javascript/php/sql to keep this race condition from occurring.

intcreator
  • 4,206
  • 4
  • 21
  • 39
busbina
  • 549
  • 1
  • 7
  • 19

1 Answers1

3

You can either lock it with a database flag, or a better strategy is to detect collisions, since this only happens in rare cases.

To detect the problem, you can save a timestamp from the database containing the last updated time. Send this along with the form, and compare the timestamp before you update the record. If the timestamp has changed, then present the user with all the data and ask them what they want to do. This offers a way for the second saving user to modify their changes based on the previously saved data if they wish.

There are other ways to solve this problem, and the proper solution depends the nature of the specific problem.

TelegramSam
  • 2,770
  • 1
  • 17
  • 22
  • Thanks for the idea about timestamps! It is easily implemented on top of my current calendar. Ill give it a try then update on how it turns out. – busbina Dec 01 '10 at 23:16