On Apr 2, 12:51 pm, dadapapa <dadap...@googlemail.com> wrote: > I managed to solve the problem. The solution is to explicitly state > the applications (models) that you want to migrate, and leave out > those that get initialized automatically when doing syncdb > (contenttypes). Here's how it worked for me: > > production server: > $ python manage.py dumpdata auth custom_apps >db.json > > development server: > $ python manage.py syncdb --settings=settings-local > $ python manage.py loaddata --settings=settings-local db.json
I'm glad you managed to solve your problem, but I would point out that using completely different versions of Django in development and production is a very bad idea. There was lots of new functionality added in 1.1, and several bugs fixed, and it would be all too easy to implement something that works in development but not in production. If your server can't be upgraded, you should use 1.0 on your development machine - it's available to download from the Django website. If you've got other projects in development which need a later version, you can use virtualenv to isolate your environments from each other so you don't get conflicts. -- DR. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
