Re: Lock
- From: Andy Klock <andy@xxxxxxxxxxxxxxx>
- To: toon.koppelaars@xxxxxxxxxxx
- Date: Sat, 10 Mar 2012 18:15:56 -0500
I actually think this is extremely relevant. Having a complete
understanding of how Oracle handles ACID is probably the first thing an
Oracle dev/dba should grasp. Now, this forum probably isn't the best place
to learn this since it is all adequately covered in the docs:
http://docs.oracle.com/cd/E14072_01/server.112/e10592/ap_locks001.htm
http://docs.oracle.com/cd/E11882_01/server.112/e16508/consist.htm
Andy
On Sat, Mar 10, 2012 at 1:49 PM, Toon Koppelaars <
toon.koppelaars@xxxxxxxxxxx> wrote:
> Why do you ask this?
> Logically those four rows will be exclusively locked by the transaction.
>
> I wonder why whether Oracle 'creates' 1 or 4 'locks' (whatever 'creating a
> lock' may mean), is of any relevance...
>
> On Sat, Mar 10, 2012 at 5:56 PM, Paul Harrison <cure@xxxxxxxxxxxxx> wrote:
>
> > Hello,
> >
> >
> > I have a table with four rows. I issue the sql statement: update table
> set
> > name = 'test'; this will update 4 rows. Will Oracle create 4 locks one
> for
> > each row or 1 lock for the 4 rows?
> >
> >
> >
> > Thanks,
> >
> > Paul
> >
> >
> >
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
> >
>
>
> --
> Toon Koppelaars
> RuleGen BV
> Toon.Koppelaars@xxxxxxxxxxx
> www.RuleGen.com
> TheHelsinkiDeclaration.blogspot.com
>
> (co)Author: "Applied Mathematics for Database Professionals"
> www.rulegen.com/am4dp-backcover-text
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
- Follow-Ups:
- RE: Lock
- From: Mercadante, Thomas F (LABOR)
Other related posts:
