Hi Russel, On 8/1/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > Yes. The problem is cause by the way that Postgres (and Oracle, AFAIK) > allocates primary keys. > > [postgres sequence explanation] > > > (Wondering why there is db-dump.py when dumpdata works.. > > but wayne.) > > It was a snippet project that was started when Django's fixture > loading still new and had some problems with edge cases (as I recall, > the particular problem was forward references in data). Rather than > contribute a fix to Django's fixture loading, limodou decided to start > a snippet project to provide an alternate implementation. > > Since that time, many problems with Django's fixture loader have been > fixed (includng the forward reference problem), and there isn't really > a need for the alternate implementation.
Thanks for the explanation Russel, it works great with dump/loaddate. I don't even have to call sqlsequencereset. :-) > > Yours, > Russ Magee %-) Kai --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
