Just wondering if anyone has tried doing quasi application based locking
with PHP? My scenario is this. I'm constructing a database for my
company to help keep track of trouble tickets, etc with a web-based
frontend. I'm using PHP (obviously =]) for inputing/retrieving data and
have a slight
() and connection_aborted() will allow
you to determine if the user has aborted, and unlock the table
accordingly.
-Original Message-
From: Barry L. Jeung [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 3:00 PM
To: [EMAIL PROTECTED]
Subject: [PHP-DB] Application-based locking with PHP?
Just
So long as you keep any referencial integrity from being broken by two
nearly simultaneous updates I don't really see much of a problem. If two
users update a trouble ticket what's the big issue? Perhaps a
notification could be displayed on the update confirmation page letting
one of the user's
Message-
From: Justin Buist [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 12:40 PM
To: Barry L. Jeung
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DB] Application-based locking with PHP?
So long as you keep any referencial integrity from being broken by two
nearly simultaneous
