On Wed, Jul 07, 2010 at 12:59:30PM -0400, tedd wrote: > Hi gang: > > I have *my way* of handling this problem, but I would like to hear > how you guys do it. > > Here's the problem -- let's say you have a database containing names > and addresses and you want "approved" users to be able to access the > data. As such, a user must login before accessing an editing script > that would allow them to review and edit the data -- nothing > complicated about that. > > However, let's say you have more than one user accessing the editing > script at the same time and you want to make sure that any changes > made to the database are done in the most efficient manner possible. > > For example, if two users access the database at the same time and > are editing different records, then there's no real problem. When > each user finishes editing they simply click submit and their changes > are recorded in the database. However, if two (or more) users want to > access the same record, then how do you handle that? Use a DBMS? I'm sorry if that seems flippant, but a DBMS handles this by queuing the requests, which is one of the advantages of a client-server DBMS. So maybe I don't understand your question. Paul -- Paul M. Foster -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
