On Nov 19, 12:25 pm, Nader <[EMAIL PROTECTED]> wrote:
> I have done it: 'python manage.py syncdb' and started the server. I
> have got the same error as before.
It seems that your content types and permissions got messed up
somehow. See this thread for a discussion of a similar problem with
some tips by Adrian:
http://groups.google.com/group/django-users/browse_thread/thread/2e873fa0309122e/56c2d5277e73d93d?lnk=gst&q=ContentType+matching+query+does+not+exist.+#56c2d5277e73d93d
> I'm in development phase but I
> wouldn't use the "DROP table' sql statements, because I have to
> installed a lot of data again. I thing there has a solution, maybe via
> 'model API'!
You can always backup your current app data with "manage.py dumpdata".
Then after a full reset and syncdb, load it back in with "manage.py
loaddata". Moreover, if any of this data is required for your app to
run, you can turn it into an "initial_data" fixture (start with the
django-admin doc link I included in my previous response.)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
