This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
in the Monkhouse DVD example (by the way it is such an orgnized and easy to follow book, thanks Monkhouse) we can find 2 levels of locking: 1. db layer, that's when we have to acquire a lock (could be read or read/write lock) before we do any operation depending on the operation. 2. inside the reservation manager, which provides logical locking.
now as a class we can't really reach to the database without going throw the facade, which gives us the ability to logically lock records before dealing with them.
so why would we still need the DB lower-level-locking (the frist one) if we are using the logical higher-level-locking anyway ?