Locking is a mechanism by which database systems can prevent conflicting access to data when multiple users are making requests to the data.
should I leave the check in the LockManager class that allows the same user to lock the same record where it has the lock or should this same user wait for the unlock of the record where it has a lock?
Free software is a matter of liberty, not price.
Free software is a matter of liberty, not price.
2) Don't use the client ID and trust that a new user of the class will do everything correctly.
4) As far as I've read, Max Habibi has some kind of soluction.
Free software is a matter of liberty, not price.
In this example, our thread could pause his execution after read the record and by then other thread could call the getRecord method or even the modify method, but if I synchronize the methods in the DatabaseFacade class this would not happen.
Free software is a matter of liberty, not price.