django - "manage.py test" fails "table already exists"

Question

I'm new to the django world. Running some tutorial apps, and when running python manage.py test i'm getting a failure saying that the table already exists. I'm not sure what is going on. I am also running south, and I got no errors when migrating the schema.

Any insight is greatly appreciated.

TIA Joey

Possibly related: http://stackoverflow.com/questions/3090648/django-south-table-already-exists — payne, Feb 03 '11 at 03:31
YES! That was it, I made some mistakes and got migration out of sync with the db. clean installs fixed it right up. — Joey Blake, Feb 06 '11 at 22:20

luc · Accepted Answer · 2011-02-07T05:48:42.880

15

It might be an error in one of your south migrations. You don't see the problem on the real db because the migration has been executed (with the--fake option maybe)

You can try to recreate the db from scracth and see if it works.

You can also disable South for unit-tests by adding SOUTH_TESTS_MIGRATE = False in your settings.py. With this option a regular syncdb will be done to create the test database. It will also speed the testing process.

I hope it helps

edited Feb 07 '11 at 05:48

answered Feb 03 '11 at 05:51

luc

41,928
25
127
172

if i have to draw db from scratch then what's the benefit of South? – Ahsan Jun 03 '11 at 11:44
@Ahsan the DB is created from scratch only for tests and it happens this way whether or not you use South. – Stephen Paulger May 25 '12 at 15:23
++ for SOUTH_TESTS_MIGRATE = False – starsinmypockets May 12 '13 at 13:24

score 3 · Answer 2 · answered Aug 15 '14 at 13:02

3

This also happened to me with a legacy code but for another reason.

I had two models with db_table referencing the same db table. I know that is stupid, but it's not my fault )

And I never found anything on the internet that could help me. I was saved by verbosity set to 3 (manage.py test -v 3) Hope this helps anyone.

class Bla1(Model):
    some_column = ...
    class Meta:
        db_table = 'some_table'

class Bla2(Model):
    some_column = ...
    class Meta:
        db_table = 'some_table'

answered Aug 15 '14 at 13:02

Dmitriy Kuznetsov

861
7
10

helped, fixed tracking which models are set to managed in a custom [TestRunner](https://dev.to/vergeev/testing-against-unmanaged-models-in-django) and keep `managed=False` in any model refrencing an already referenced table. – Evhz Jan 21 '20 at 19:19

score 0 · Answer 3 · answered Aug 02 '13 at 15:16

0

This happens also with Nose when
--cover-package=userdata,incorrectname
One of package's name is incorrect

answered Aug 02 '13 at 15:16

Bartosz Dabrowski

1,850
2
15
21

score 0 · Answer 4 · answered Sep 10 '11 at 21:42

0

and if you are testing with nose:

DST_RUN_SOUTH_MIGRATIONS = False

answered Sep 10 '11 at 21:42

allo

3,955
8
40
71

score 0 · Answer 5 · answered Dec 27 '22 at 07:11

0

You have to similar models, check it

answered Dec 27 '22 at 07:11

Muhammadalive

648
5
5

django - "manage.py test" fails "table already exists"

5 Answers5

Linked