C
ChUIMonster
Guest
While I'm at it... Even if you are using the partition aware flavor, ROWIDs are a very poor choice for a unique identifier for quite a few reasons. Among the many other reasons that this is a bad idea -- over time records almost certainly get deleted from the DB. Those ROWIDs will be reused. Even if that never happens someone may eventually come along and dump & re-load your database. Or the table might be moved from one area to another. Or a new partition might be created. The ROWIDs can change when those sorts of things happen and the value that you have stored will no longer match. (BTW -- how are you planning to store the ROWID? As a string? ROWID isn't a valid datatype for a db field...) As another aside -- if you're thinking that the ROWID will give you a magical sequencing of the order in which records were created that would also be wrong.
Continue reading...
Continue reading...