Hi Andrew,
Perhaps I shouldn't be replying since I don't think I'm understanding your
question fully.
When you wrote:
"with each entry having a unique id"
did you mean that you are creating a unique identifier, or instead that you
are making use of the ROWID within sqlite?
Regarding:
"it is my understanding that a SELECT command will treat both databases
as one and so return potentially overlapping ids"
Can you elaborate on that understanding? Sqlite 3 can create transactions
that are atomic across multiple databases (if the main database is not an
in-memory one), but I'm not sure what "treat as ... one" would otherwise
mean.
Even for a single database, ROWID values are unique ONLY within a particular
table. Therefore (to my understanding) if you call out a particular
database, a particular table, and a particular ROWID, then you've uniquely
identified a row.
Dan Kennedy just referred to the ATTACH documentation which may be helpful:
http://www.sqlite.org/lang_attach.html
Donald Griggs
Opinions are not necessarily those of Misys Healthcare Systems nor its board
of directors.
-----Original Message-----
From: Andrew Gatt [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 04, 2005 6:56 AM
To: [email protected]
Subject: [sqlite] ATTACH, query and differentiate
