Re: Re: MySQL Database Locking - needed?

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 At 16:30 10/07/2001 -0700, you wrote:

Tom Peck wrote: Thanks for the reply Manual. The updating IS done with one single query - but the problem is that if two people are editing the same car, the second update will overwrite the first. Not a huge problem - and the chance of it happening is almost nil - but there is still the possibility.. Changing databases seems a little extreme - and not possible with our web host. Tom How about writing a text file that would be your "lock" file, rather than depending upon MySQL to do it for you? -- Raquel ============================================================ He who has imagination without learning has wings and no feet. --Anonymous