Matt, First, a question of this sort is better suited to django-users, as django-dev django-dev is for discussion of the development of Django itself.
Second, from what I can tell db_dump.py is not part of the official trunk -- thus I'm not familiar with it. My priority is to have compatibility with the features already within Django before I worry about third-party scripts. Finally, `django_session_id_seq` tells me that the error is related to the sessions framework, django.contrib.sessions (which is included in INSTALLED_APPS by default). In the code for the Session model, the primary key is manually specified for the `session_key` field -- therefore no AutoField is created for the Session model. My guess is the bug lies with the script's handling of models that use primary keys outside the implicit AutoField -- most likely this is not related to GeoDjango. -Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
