Re: "NOWAIT"

From: Rod Corderey <Lane_Associates_at_compuserve.com>
Date: Fri, 08 May 1998 12:58:14 +0100
Message-ID: <3552F356.14EF5FF8_at_compuserve.com>


Hi Nicholas,

it depends on how the inserts are being executed, whether by a form, and which version, or whether by a PLSQL procedure or whether by a trigger.

There are different options depending on the scenario.

Could you post a little more information?

regards

Rod Corderey

Lane Associates
Lane_Associates_at_Compuserve.com
http://www.Lane-Associates.com

Stephanie Panagopoulos wrote:
>
> Could you please help us with the follow problem.
>
> Table A has two keys.
> Field pk is a primary key and uk is a unique key.
>
> A session inserts into A the record (pk_vall, uk_vall) successfully.
> The session does not commit the insertion.
> Another session does attempts to insert the same record and because
> there is
> the uncommitted previously inserted record from another session has to
> wait until
> the first session execute a commit or a row back releasing the row-lock.
>
> We want to change the above scenario.
> What we want is to make each session attempting to insert a record to be
> able to
> understand that at the specific moment a row-lock for the specific row
> exists and
> abort the insertion immediately.
>
> We may say we need a "NOWAIT" behavior for the insert operation.
>
> Which is the best method we can accomplish what we need ?
> ( We are looking for a work-around solution)
>
> Thank you very much
>
> Nicholas Economou
Received on Fri May 08 1998 - 13:58:14 CEST

Original text of this message