Re: Record Locking ???

Jim,

Business need: a good question .... I guess he is afraid of others writing on top of his entry.

In 1) I should provide an error message that the values were changed while he had the record and refresh his screen with the new values?

In 2) If the guy doesn't come back to his terminal and commit the changes, he'll never be able to get the records unless an administrator unlocks it for him?

Mike

Jim Kennedy wrote:

> He can't prevent others from reading if that is what he wants to do. (unless
> he does select for update).
 

> Two methods,

1. one is to do the update with all the original values in the where clause and if the record is not found then it changed under him. 2) Another is to do a select for update. Then others won't be able to change records that are in the select until he does a commit. In a sessionless environment (web) this might be a challange. (eg

> leave records locked since the user might just not come back to finish)
> What is the business need?
> Jim
>
> --
> Replace part of the email address: kennedy-down_with_spammers_at_attbi.com
> with family. Remove the negative part, keep the minus sign. You can figure
> it out.
> "Michael Hill" <hillmw_at_ram.lmtas.lmco.com> wrote in message
> news:3EB91205.2C063F50_at_ram.lmtas.lmco.com...
> > I have a Coldfusion web application that makes calls to Oracle tables,
> > inserts, updates, et. al and one of my users wants to add "Record
> > Locking". I am thinking this is not practical and is only valid in a
> > client-server environment.
> >
> > Am I wrong?
> >
> > Comments?
> >
Received on Wed May 07 2003 - 18:22:24 CEST