On 4/4/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > All we can do is set the > next sequence value to one greater than the largest existing pk value; > there's no way to tell the automatic sequence to skip a particular value > in PostgreSQL.
That's the solution I was hinting at without trying to lead the witness. I wasn't aware of a way to do this, and it looks like that's because there isn't a way to do it :-) There is already sequence resetting code in management.py that pushes the sequence to the maximum existing value; it's just not a generic call across database backends. I'll factor that code out behind a generic backend, and add a call to the generic reset code to loaddata. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
