This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In the Data(access) class, we should wrap read/delete/create/update in lock/unlock ?
In the DB tier, I did not wrap read/create/update/delete in lock/unlock. Just,in the booking method of GuiController class(GUI tier), I wraped the update in lock/unlock as follows,not Data (access) class.
The assignment does not require other funtions except booking. So,I think that others(create/delete/read) do not need wrapping. Of cource, If the assignment required me it, I would wrap others.
Am i right?
[ February 20, 2007: Message edited by: james bonds ]
Yep I think that is a good approach and is very similar to how I have also done this. No need for create and delete in your gui so there is no need to wrap these. BTW - Create does not require a lock/unlock as the record does not exist before the method completes.