Sorry...That's what I meant - scary you can insert into a table that has this property without first setting The propert off without re-seeding - ie. How Sybase and SqlServer handle this..
It would be good if this was documented a little clearer.... Thx all for your assistance - onward and upward (so to speak) Cheers... > -----Original Message----- > From: Kurt Welgehausen [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 9 March 2004 2:34 AM > To: [EMAIL PROTECTED] > Subject: Re: [sqlite] Resetting primary key auto-increment > after table re-create > > > > So what you are saying is that if I recreate the table I can insert > > all the old values back into the newly created table (including the > > primary key values) and the primary key column wont > complain? That's a > > bit scary! > > It's not scary, it's essential. In a real database, an > integer primary key will almost always be referenced by one > or more foreign keys. Changing the primary key would destroy > referential integrity. > > Regards > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
