On 4/4/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > I can work around this problem in a messy way in the deserializer by > manually resetting the sequence to the largest PK value that was found > during deserialization, but that isn't really clean, and doesn't fix > the manual allocation problem.
AFAIK the only way around this is to remember the largest PK value used during the data insert, and manually set the sequence to start above that. As Malcolm pointed out, Postgres expects you to manually update the sequence any time you do something that bypasses the automatic values. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
