Peter,
Peter Bozek wrote:
On 10/16/06, Youri <[EMAIL PROTECTED]> wrote:
Regarding the Unique ID being an Integer, how can I trust an Integer to
be unique?
If this "rowid" is generated by SQLite, how will it be treated when
exporting datas out of the DB and back? How to maintain the "link"
between tables if I use these rowid for JOINS?
SQLite ensures that rowID is unique. However, your concerns are valid
and IMHO rowID has a limited usability as a primary key. In more
complex databases you should define your own primary key. There are
many ways how to do that:
- use Max function
- use separate table to store next sequence ID
- use build in support for defined sequences, if db supports it
(SQLite IMHO does not support sequences, but most other databases do)
If this is what I mean, I saw something in the demo version of
SQLiteManager from SQLabs. When you define your Column in a Table there
is an option called "autoincrement". Is this what you meant?
- use UUID.
I don't understand UUID. Can you please develop the meaning?
Youri
I used to use first two, but now qtry to switch to UUID, as it solves
quite a few problems (like export-import of data).
Related questions - do somebody have Declares for obtaining UUID from
MAC OS X and Windows?
_______________________________________________
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>
