Here's some more info in case it helps: The "manage.py test" call seems to get as far as creating the table "django_migrations", then things break. The production DB has several more tables (25 in all) I'm not seeing in the output below, so I guess this issue must be related to the migrations table in some manner.
All the best, Uwe ############################################################ MariaDB [test_club300_owl]> show tables ; +-----------------------------------------+ | Tables_in_test_club300_owl | +-----------------------------------------+ | club300_alert | | club300_area | | club300_bird | | club300_birdcategory | | club300_birdcategory_birdcategory_birds | | club300_country | | club300_location | | club300_newsitem | | club300_observation | | club300_toplist | | club300_toplist_toplist_birds | | club300_userprofile | | django_migrations | +-----------------------------------------+ 13 rows in set (0.00 sec) > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1267ddd2-b62b-4509-bd71-b95c6a844375%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
