Re: Recommendations For Select for Update Statments

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Tue, 12 Apr 2016 18:44:44 +0100
Message-ID: <CABe10sa4YEPSgkp6uvUzscC1ow0Bm5oaVWS4SWMgbiwjepEv2w_at_mail.gmail.com>

Surely if you have the means to change the SELECT FOR UPDATE statements you can take out the for update in most/all cases? If you can't change the statements then surely there's no benefit in seeking alternatives. On 12 Apr 2016 12:33, "walid kaakati" <dmarc-noreply_at_freelists.org> wrote:

> Hallo List,
>
>
> I working on an application that generates SQL Statements with *SELECT
> FOR UPDATE* clause, these Statements cause a lock on the select rows and
> hence blocking other sessions,sometimes the lock stay for half an hour
> according to the selected data.
>
> From analzying the Locks ,i found the locking due to Logical Errors in the
> development of the applciation .
>
> My question from PL-SQL viewpoint is their an alternative for this
> mechanisem that requires a lock on the Selected rows for Update ? any
> recommedation to minimize this Locking ?
> my (Database is 10g ).
>
>
>
> Best Wishes,
>

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Apr 12 2016 - 19:44:44 CEST