Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Locking issues
In article <330a6c1c.4042803_at_nntp.mediasoft.net>,
tkyte_at_us.oracle.com wrote:
<snip>
> If you are worried about someone walking away from a terminal, perhaps your
> client server application should have a timeout in it. If no keyboard
> activity/whatever, issue a message, give them one more minute or something,
> and then rollback.
Good suggestion, only how would one do this... start a timer in the on-lock trigger, or what? I would like to know of anyone has successfully implemented this function, and how it is done. It is a problem that worries me as I work on forms that will be used in a busy OLTP environment.
> What has been suggested as a locking scheme is:
>
> 1.) I read out a list of records and display them (no locks)
> 2) user attempts to update COPY of record 1, goto database and lock record 1
> ensuring that the local copy matches the database copy, return error if record
> is locked OR has been modified.
> 2a) do the same for records 3 and 5
> 3) program issues 3 updates
> 4) database is consistent.
Not only suggested, but also implemented in Forms. This works quite well, except for the operator inactivity problem.
Steve Cosner
<snip>
>
> Thomas Kyte
> Oracle Government
> tkyte_at_us.oracle.com
>
> http://govt.us.oracle.com
>
> ---- Check out Oracle Governments web site! -----
> Follow the link to "Tech Center"
> and then downloadable Utilities for some free software...
>
> -------------------
> statements and opinions are mine and do not necessarily
> reflect the opinions of Oracle Corporation
-------------------==== Posted via Deja News ====----------------------- http://www.dejanews.com/ Search, Read, Post to UsenetReceived on Thu Feb 20 1997 - 00:00:00 CST