On Oct 16, 2006, at 3:52 AM, Þór Sigurðsson wrote:
You can trust the rowid to be unique - while the data is in the DB.
Well ... that would the the right behavior. It's only unique considering the data that is currently in the table.
If you insert 100 rows then delete the last 50 (rows 51 - 100) and insert 50 more rows the rowid for the last 50 will be the same as those that were deleted (ids 51-100) If you insert 100 rows, and delete the first 50 (rows 1-50) and then insert 100 more the new rows will have rowids sequenced after the existing rows (ids 101 - 200)
It almost behaves like it does a max(rowid) + 1 on the existing data Try it
At the moment you export the data, you cant, since you should never try to insert the rowid yourself. The best solution is to normalize your data so that each table is left with a unique identifier ( primary key ) for you to work on, and leave the rowid to the db's perusal.
Yes You should NOT use rowid because of the issues I've pointed out _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
