Vivek,
Bad, bad, bad idea. You can play with rowids in your programs - as long as you
consider them to be transient values (get it/use it). Don't forget that they are
physical addresses (BTW, DBMS were invented in the first place to hide the physical
implementation from programs). Any
You can use the rowid but do not keep it.
As a dev DBA I would not allow to store the rowid in a
table because its value is meaningless once you
export/import, ...
--- VIVEK_SHARMA [EMAIL PROTECTED] a écrit :
let us suppose there are two tables M and P.
both Contain the field emp_id. other
Developers can also use the approach that Oracle uses with
UROWID values, which are stored in secondary indexes on IOTs
(i.e. replacing ROWIDs used in normal indexes).
Store the ROWID as well as the PK/UK column values. Use the
following algorithm to retrieve in future:
1. Retrieve the PK/UK
