On 9/8/06, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>the updlock with SQL server doesn't prevent data reads occurring when > lock is in > place. > > Sure, and no one wants to prevent reading during that time. > BUT it will certainly prevent another updlock on the same record, thus > prevent someone to read it for editing also.
Which in turn means that your app design has to be built so that there is a 'view' screen' and a subsequent 'edit' screen, or the user has to in some other way positively activate an edit mode separate from a viewing mode. I've built apps like that in the past and I have yet to see a client happy with the fact that they have to do a 2-step process rather than a single step (i.e. the viewing screen is the edit screen). Its a situation where only the programmer likes the idea. s/he is making their problem the users' problem. Instead the app should be designed with the user experience in mind and the underlying mechanicals should conform accordingly. Handling this at the application level meets that usability goal. My own systems allow the user to see the data but there is no 'save' button onscreen, and typically a big red message informs them the record is in use by User X. Often they are granted the option of contacting User X, and User X's lock will expire after a set amount of idle time. further, an admin can break User X's lock manually in a pinch. While talk of db-level operations is fine as an intellectual exercise, these are not the sorts of things that make any sense to manage at the db level. You have to provide a level of user interaction in a fully featured app. Doing a row lock is MAYBE acceptable for the simplest apps but not in something enterprise level, or arguably any level. -- [EMAIL PROTECTED] Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252578 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
