Ahhh, ok a good idea. I will think about it some more. Thanks Tom At 16:55 10/07/2001 -0700, you wrote: >Tom Peck wrote: > > > > > >How about writing a text file that would be your "lock" file, rather > > >than depending upon MySQL to do it for you? > > > > > >-- > > >Raquel > > > > So what you mean is: > > > > If someone clicks on a car to edit, a txt file is written (maybe called the > > carID.txt). Then if someone else clicks on that car to edit it, it says > > that it is already being edited by someone else because the txt file > > exists? So what happens if that person who clicked first closes his > > browser before updating the car? How can that text file be automatically > > erased? > > > > I think I'll just assume that this wont be a problem, and if someone > > overwrites someone elses edit then too bad.. :-) > > > > Tom > >Why not check the date/time the file was created? If an arbitrary >amount of time has expired (2 minutes? 5 minutes?) then you create your >own lock file as if the first wasn't there? > >-- >Raquel >============================================================ >He who has imagination without learning has wings and no feet. > --Anonymous -- PHP Database 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]
