Reply-To: "Frank" <franjoe@frisurf.no>
From: "Frank" <franjoe@frisurf.no>
Newsgroups: comp.databases.oracle.misc
References: <3B1C2201.2781@rswheeldon.com> <N5cT6.6794$lM3.133810@news1.oke.nextra.no> <3B1E75FC.15FB@rswheeldon.com>
Subject: Re: Determining a PK for a view
Lines: 19
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <ZbxT6.28904$lM3.143799@news1.oke.nextra.no>
NNTP-Posting-Host: 130.67.136.34
X-Complaints-To: news-abuse@nextra.no
NNTP-Posting-Date: Wed, 06 Jun 2001 23:24:09 MET DST
Organization: Nextra Public Access
X-Trace: readme.online.no 991862649 130.67.136.34
Date: Wed, 6 Jun 2001 23:23:20 +0200


Hi

> I was under the impression that insertions/deletions were unlikely to
> affect the rowid of another entry under normal circumstances. When will
> they
> change? Change due to an explicit DBA reorganization can be tolerated.
>

I mention the DELETE/INSERT cycle as a example; if you DELETE a row, the
perform some stuff, and INSERT it again (God knows why :-) I wouldn't
speculate in whether Oracle places the row in the same place as it were (the
database wouldn't "know" that is was the same row). I will agree that this
very explanation is probably not a big killer for you though unless you do
those kind of operations :-)

Frank