Re: Locking records accross multiple php pages
Perhaps an alternative is to implement programmatic "locks" on rows -- add two fields: who locked it, and when.
When the user ('who') comes back, the lock can be seen and refreshed.
When someone else (not 'who') looks at the row, the application must do whatever the business logic requires to say "no, no, not now".
When the user gets distracted for too long (`when` < NOW() - INTERVAL 20 MINUTE), then the 'lock' is consider to be unlocked. This lets you avoid unfixable lock situations.
Subject
Written By
Posted
Re: Locking records accross multiple php pages
July 17, 2014 04:37PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.