> -----Original Message----- > From: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users- > boun...@mailinglists.sqlite.org] On Behalf Of R Smith > > As an aside - I've always prescribed generating your own ID's. There is no > requirement for using AUTOINCREMENT in any DB - It's a lazy method for > creating an easy sure-to-be-unique ID list for simple inserted rows, and > brilliant for stuff like log files or such, but I would make effort to avoid > it > where one can manage the IDs another way. Palming that responsibility off > to the DB engine is surely easier, but less optimal, if only in more complex > and foreign key designs. >
I agree 100%. I always generate my own ID's. I have a generic insert() function that returns the last inserted row id. I never do anything with the returned value. It's just there. -- Bill Drago Staff Engineer L3 Narda-MITEQ 435 Moreland Road Hauppauge, NY 11788 631-272-5947 / william.dr...@l-3com.com CONFIDENTIALITY, EXPORT CONTROL AND DISCLAIMER NOTE:This e-mail and any attachments are solely for the use of the addressee and may contain information that is privileged or confidential. Any disclosure, use or distribution of the information contained herein is prohibited. In the event this e-mail contains technical data within the definition of the International Traffic in Arms Regulations or Export Administration Regulations, it is subject to the export control laws of the U.S.Government. The recipient should check this e-mail and any attachments for the presence of viruses as L-3 does not accept any liability associated with the transmission of this e-mail. If you have received this communication in error, please notify the sender by reply e-mail and immediately delete this message and any attachments. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
