Re: Asynchronous Commit in Oracle Database 10g R2

From: VC <boston103_at_hotmail.com>
Date: Sat, 3 Sep 2005 09:27:57 -0400
Message-ID: <qdCdnWV0NZtKOYTeRVn-vg@comcast.com>

<xhoster_at_gmail.com> wrote in message
news:20050902221630.086$YG_at_newsreader.com...

> "VC" <boston103_at_hotmail.com> wrote:

>> <xhoster_at_gmail.com> wrote in message
>> news:20050902202109.103$g4_at_newsreader.com...

[skipped]

Thank you for the clarification.

>>
>> >If this is a problem, you shouldn't be
>> > commiting in the loop anyway, asynchronously or not.
>>
>> If you mean committing inside a PL/SQL proc, then arguably one should
>> not be doing so at all.

>
> Well, I wouldn't argue that.  Surely someone has to commit somewhere, and 
> I
> see no reason to think it is somehow OK for Java or Perl or C++ to issue
> the commit but not for PL/SQL to do so.

The reason is having no control over transactions from the client side (when one commits in a PL/SQL proc.) as wrote elsewhere. Perhaps, there are cases when doing so is safe, but they surely must be rare.

>

>> I do not understand your using the word
>> 'asynchronously' in the last sentence, though.

>
> By "asynchronously" I simply meant the type of commit that doesn't wait.
> Maybe I misused the term.

Thanks.

>
> Xho
>
> -- 
> -------------------- http://NewsReader.Com/ --------------------
> Usenet Newsgroup Service                        $9.95/Month 30GB 

Received on Sat Sep 03 2005 - 08:27:57 CDT