There's something about this on the SQLite website which I can't
find right now, but the upshot was that if you want to be able to
anticipate recent future values for your primary key, you should use
a field you can calculate, not autoincrement
On 3 Jan 2006, at 23:08, Dave Howorth wrote:
On Tue, 2006-01-03 at 12:35 +1100, Kim Ryan wrote:
One remaining concern is the integrity of the key. I think I will
also
create a unique index based on my unique columns, to ensure I never
get duplicates rows.
That's what I do.
Probably a rare occurrence, but I have read that auto increment
should
not be relied on for row uniqueness.
If autoincrement doesn't work that would seriously break my
application :( Where did you read it?
Cheers, Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through
log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Maypole-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-users
