Re: Automatic Locking

From: OraCLeDbA <oracle_dba_at_zdnetmail.com>
Date: Wed, 26 Aug 1998 21:09:36 -0700
Message-ID: <6s2lth$3ne@dfw-ixnews7.ix.netcom.com>

The first person who issue the command will get an exclusive lock on the row and table. When the second user issue another DML command (except select) on that table, the user will not get any response until the first person issue a commit statement.

Winnie

Bernadette Pinto wrote in message <1998082619055476740_at_zetnet.co.uk>...
>I need help on this urgently. Please respond!!
>
>My problem is this:
>
>Can someone explain (in beginner - speak) how automatic locking is
>handled in a multi - user environment? I am particularly curious
>about two users who are performing DML upon the same table but not
>committing their actions. What will happen when one commits before
>the other? What will happen to the row / columns which have been
>deleted when the other user attempts to update them?
>Are the table.rows flagged as deleted and thusly locked to the other
>user? Or, if the updating user manages to update first are these rows
>flagged as updated and thusly inaccessible?
>How does it work? I really appreciate any answer.
>
>Thanks
>
>B. Pinto
>
Received on Wed Aug 26 1998 - 23:09:36 CDT