On 8/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Then, I am have exported data in all various formats, with hope that > one of them would work: > > ./manage.py dumpdata --format=python > data.python
Python fixtures aren't really intended for use by end users - its an internal format that makes the YAML and JSON serializers easier. That's why the extension is .python, not .py. This explains the error you see for the python serializer. > ./manage.py dumpdata --format=json > [EMAIL PROTECTED] ./manage.py > dumpdata --format=xml > data.xml >From the looks of it, the problem you are experiencing is caused by the fact that you are dumping the _entire_ project, not just the application with data you are interested in. This includes all the admin tables, the permissions tables, etc. Try running: ./manage.py dumpdata --format=json --indent=2 myapp > data.json This will dump the data for a single application. For most simple purposes, this will be all you need to dump. Digging a little deeper - If I'm reading the error message correctly, this error is occurring because you are using MySQL with InnoDB tables. Have I guessed this correctly? If so, you should be aware of the issues that exist with MySQL and InnoDB tables: http://www.djangoproject.com/documentation/django-admin/#loaddata-fixture-fixture Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
