Ah, yes, the docs aren't clear on this at the moment, but the automatic schema creation does not run if you use migrations for an application. You will have to create a migration that creates the tables. (Just use 'python manage.py sqlall' to get the sql for the migration)
The reason for this is that syncdb will create the schema based on the latest version of your model. But when you're rolling out to a live server you need to be able to run the migrations to bring the schema up to date, so you need to know exactly what stage your schema is at, so you have to run all your sql through migrations. If you create a migration that sets up your table structure do the tests run ok? Mike On 4/20/2007, "David Marko" <[EMAIL PROTECTED]> wrote: > >Thanks for an advice. I found problem with migrations when running >tests - python manage.py test . It seems that migration is run before >django creates table based on model. Tests should probably not run >migratons at all. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
