Well here is the situation. 1. Jack opens record A to change an entry. 2. Jill opens record A to change an entry. 3. Jack finishes his changes and saves the data. 4. Jill finishes her changes and saves the data.
Jill just over wrote whatever Jack did. The only method I could think of to prevent this was to have the client check to see if the record was allready being edited by someone. If it is then they have to wait. Is there another way to do this? What are atomic updates?? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
