newbie row locking question

Hello Jim,

it would take up too much space to explain the entire Oracle locking mechanism, but to answer your question: no, you do not need to explicitly lock rows in your applications. Oracle will take care of this, automatically 'write protecting' the row you are updating, while still keeping it readable for other users.

Hope this helps,
Bas

> -----Original Message-----
> From: Jim Haran [SMTP:jim_haran_at_datasoft-inc.comREMOVE_THIS]
> Posted At: Tuesday, October 20, 1998 3:41 PM
> Posted To: server
> Conversation: newbie row locking question
> Subject: newbie row locking question
>
> Hello all,
> As a recent newcomer to the Oracle world, there are a few
> questions
> I have. I have not come across documentation that covers row locking.
> In
> the old world (xBase), I would lock a record as soon as the user
> accessed it. As such, if another user attempted to edit the same
> receord, the lock would be detected and a dirty read at best would be
> allowed.
> Do I need to explicitly lock rows in my apps? If not how does one
> control possible concurrent updates to the same row? I'm sure this is
> covered somewhere in the documentation but I have'nt found it. Thanks
> in
> advance for any help.
>
> Jim
Received on Fri Oct 23 1998 - 13:01:32 CDT