The problem is that unlock() will throw an exception since the record is already deleted, according to the programming spec., but I do want unlock() to successfully return as the client did nothing wrong.
Any suggestion how to implement delete() with locking?
Any methods that throw RecordNotFoundException should do so if a specified record does not exist or is marked as deleted in the database file.
Originally posted by Bridget Kennedy:
The DBAccess interface requirements suggest features that are not addressed in the business layer list of 'must haves'. Does anyone know if we are required to provide a GUI interface to delete, create, and/or edit records? If not, does that mean that we provide DBAccess implementations that never get called in the system as delivered? Seems too good to be true.