Re: where rowid = ...

Well, I wouldn't be relying on it in the sense of hard-coding it into my application. Not with the 'move tablespace' command so ready to hand (in 8i, natch).

One export, drop and import later, and the rowid in the code has just gone west, too (any version you care to mention).

As for the indexes working pretty darned well... mmm, Move tablespace requires a rebuild of the indexes. Import causes indexes to be re-created. And then there's the little matter of row migration, where the index simply points to the wrong place, and we have to do two i/os to retrieve the row.

And the rowid for an IOT would be, er, what exactly?

So no, it's not a bunch of nonsense. Rowids have their uses, but strictly limited.

HJR

--
=============================!!=============================
The views expressed are my own only, and definitely NOT those of Oracle
Corporation
=============================!!=============================


"Daniel A. Morgan" <dmorgan_at_exesolutions.com> wrote in message
news:3B26F78A.6339147B_at_exesolutions.com...


> Alex Filonov wrote:

>

> > Steffen Ramlow wrote:

> >

> > > how efficient is a whereclause like:

> > >

> > > where rowid = '...'

> >

> > It's the most efficient. And most stupid, too. You can never rely on

> > rowid, read documentation.

>

> That is a bunch of nonsense left standing alone as you wrote it. There

> are certainly situations where it can not be relied upon. But there are

> an awful lot where it is the best, most efficient, method of locating a

> record.

>

> If you are going to make statements such as you did you should qualify

> them with the specific conditions under which they are true. You might,

> for example, note that EVERY index in Oracle locates records by their

> rowid and that seems to work pretty darned well.

>

> Daniel A. Morgan

>