On Feb 16, 2008, at 8:31 PM, Brett wrote:
> > > I have to be able to dump my tables to CSV so I need to keep the > primary > key values so my foreign keys match up. > > Michael Bayer wrote: >> >> On Feb 15, 2008, at 5:53 PM, Brett wrote: >> >>> serial column instead. On sqlite the id column seems to always >>> generate >>> a unique number. I'm not sure what other databases do. What's the >>> best >>> way to address this? Here's an example of whats happening: >> >> why not rely upon the sequence unconditionally ? SA has arranged >> things such that if you never create your own PK values, the >> database's preferred methodology is used automatically (i.e. sqlite's >> or mysql's autoincrement, PG's SERIAL/sequence). >> after populating the tables with your CSV data, manually increment the sequence to the next available id. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
