I have (tried running migrations), although I didn't change my models and I'm not sure if I did it after or before the problem started.
You're probably right though, if the current database has issues but not the new one, the old one might have somehow been corrupted... It's probably a good time to switch to my PostgreSQL server. I'll do the transfer once I get a chance. I still find it odd that Django reports a different table name than the traceback. Thanks, Michel -- 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 https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/820df496-4a89-4044-89c5-091f48e15efe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
