Another thing that I recall, if I am correct, the freed ROWIDs (after
deleting rows) are assigned to newly inserted rows.
Aleem
-Original Message-
Sent: Thursday, February 21, 2002 11:18 PM
To: Multiple recipients of list ORACLE-L
Subject:ROWID datatype columns and
In my previous job, ROWIDs were used left-and-right for performance benefits
(accessing a row using ROWIDs is the fastest)and were integral part of the
Appl Design at that time. Other than performance, I do not know why one
would want to use it. However, it prevented us (Tech Support, SDBA) from
Oracle changed the ROWID size between Oracle7 and Oracle8. It went from 6 bytes to 10
bytes. So if a developer wrote code that only sized the ROWID to 6 bytes, it's
probably not going to work when converted to Oracle8 or 9.
Jerry Whittle
ACIFICS DBA
NCI Information Systems Inc.
[EMAIL
I am sure someone has a reason for creating a column with a ROWID datatype
but I cannot think of it. Every row has a ROWID column anyway so why
create another one. That column would have to be kept update on almost any
kind of DDL performed on that table. I cannot imagine populating
that field
ROWID's have their place. My preference is that they are used in PL/SQL
or other code as a means of quickly locating or relocating a row in a
table.
Using them procedurally at runtime is generally considered a valid use
of ROWID data types.
Storing ROWID data is generally considered a bad
Patrice,
The only reason I can think of creating a column with a datatype of ROWID,
is in order to store a rowid. Why you need to store the rowid escapes me
as the rowid is available as a pseudocolumn anyway.
It is also dangerous to store this rowid in a column, as it can change.
During and
A rowid column can be put to very good use in transitional tables for batch
processing or temporary tables. For example, check out the CHAINED_ROWS
table that Oracle creates via the utlchain.sql script. I've seen this
technique in the commercial Banner Utilities application from SCT. It may be
a
