You could always lock a record and only allow that user to see the locked files (maybe showing an icon indicating that it SHOULD already be checked out in another browser window and ask if the user still wants to open the file (in the case of a computer crash or they closed their browser without properly checking the file back in, etc). Keeping hits on a database to a minimum is a good goal, but databases are meant to be used and abused too.. So don't be afraid to do a little select or update from time to time. It's when you do things like "select * from MillionRowTable" repeatedly that you have issues. :) Good luck! -TG > -----Original Message----- > From: SCALES, Andrew [mailto:Andrew.SCALES@xxxxxxxxxxxxxxxxx] > Sent: Tuesday, November 30, 2004 9:45 AM > To: php-db@xxxxxxxxxxxxx > Subject: RE: Multi-User Update Problem > > > Thanks very much for your help. The main difficulty I was > having really was > unlocking the record again if the user crashed out or just > closed down their > browser/computer (something they have a bad habit of doing) > but storing the > time the record was locked and ignoring the lock if it's over > that time > sounds interesting. > I may try storing the data in a session variable and then > comparing that to > the database before the updated data is inserted into the > record as Bastien > suggested. We wanted to keep hits on the db to a minimum, but > seen as some > extra traffic will be necessary anyway I may just try that. > > Thank you both for the advice, > Andy -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
