Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: why frequent commits are not good?

Re: why frequent commits are not good?

From: Nuno Souto <nsouto_at_nsw.bigpond.net.au.nospam>
Date: Sat, 17 Mar 2001 15:11:57 GMT
Message-ID: <3ab37d8a.21911729@news-server>

On Sat, 17 Mar 2001 15:28:48 +0100, "Frank" <franjoe_at_frisurf.no> wrote:

>I dont speak these lock-flags fluidly, so I wonder; what exactly is locked
>(see
>NetComrade's posting) when doing this query?
>
>select empno,ename from emp_at_remotedb;
>
>And does this raises a lock locally so that no other session on the local
>datababase
>can query the same remote table until commit/rollback?
>

Rule #1 when dealing with ORACLE:
A SELECT without the FOR UPDATE clause will *NEVER* lock a row, table, database, other query sessions, whatever.

Cheers
Nuno Souto
nsouto_at_bigpond.net.au.nospam
http://www.users.bigpond.net.au/the_Den/index.html Received on Sat Mar 17 2001 - 09:11:57 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US