Thanks for your reply... I havent found any reference to this in the doco so Im not sure how any of this might work..
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! Even if this is true what happens when I next insert a value (normally without specifying the primary key field) - does it just pick up the latest? I guess I will have to try this but it all sounds a little confusing... Any one tried this? > -----Original Message----- > From: Will Leshner [mailto:[EMAIL PROTECTED] > Sent: Monday, 8 March 2004 3:47 PM > To: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> > Subject: Re: [sqlite] Resetting primary key auto-increment > after table re-create > > > > On Mar 7, 2004, at 8:51 PM, Roger Hawkins wrote: > > > turning off of auto-incremement > > then I do my insert of old table rows into new table > > and then turning back on auto-increment with a seed value (starting > > point) > > would be the way to go. > > > > If you specify a value for the primary key when you do the > insert, then > that is the value that will be used (assuming it is unique). > Won't that > work? > > > --------------------------------------------------------------------- > 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]
