By "normal database" I meant the one that gets used normally by Django, e.g., while running the development server (manage.py runserver)--in contrast to the test database.
Thanks for the pointer. I checked my INSTALLED_APPS, and somehow I'd missed a module. I'm not sure how that happened, since the appropriate tables did exist in my normal database, and I don't have any idea why I would have removed the appropriate line after I already had it set up properly. Adding back in the missing module, the test worked as expected (and all necessary tables are created). Thanks for the help! On Sep 15, 9:52 am, Karen Tracey <kmtra...@gmail.com> wrote: > I don't know what you mean by "normal database". The test runner > essentially does a syncdb on the test database -- thus, it will create all > the tables for all the models for all the apps listed in INSTALLED_APPS. If > you are seeing behavior different from this we'll need more specifics about > what exactly you are doing and what tables, specifically, are missing in > order to help figure out what is going on. > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
