On Thu, Apr 2, 2009 at 9:23 PM, Andrew G. <agross...@gmail.com> wrote: > > I have a django app that is built against an existing database. In > the database, there are a couple tables used as the many-to-many > relation lookup table. However, I have mapped models to the many-to- > many lookup table, since I have a need for accessing these entries > directly. Since the tables already exists, manage.py syncdb has no > problems, but when running manage.py test, the attempt to create the > test database complains that the many-to-many table already exists and > fails out. > > Is there a way to specify ignoring the creation of this table > somewhere, or another way to circumvent this problem? Should this be > considered a bug?
I'm not sure I understand your situation here. When you run manage.py test, Django creates an entirely new, clean database. There shouldn't be any pre-existing tables. Can you elaborate on exactly what you are doing to generate this error? 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
