Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Table Design!
The example you provided probably solve the requirement that the OP was
after ... or it may not, if the database is shutdown, or the user
looses his connection before doing a commit (or does a rollback), or
another user does a select nextval ...
The problem I am aware of is when there is an expectation that the
generated unique record identifier has an additional business meaning
or has other restrictions. Common miscomception are that the order of
the number is significant, or that there wont be or should not be
'holes' in the sequence. There will be sequence numbers that wont be
used (skipped over), and even though the numbers will be issued to
individual sessions in order, they can be commited in any order, and
where the rows is saved in the table/segment/disk file is not impacted
in any way by the value of the sequence number.
Received on Mon Nov 14 2005 - 12:13:29 CST