Hello. We're migrating someone else's app that was at Django 1.5.12 and we're trying to bring it more up-to-date, step-by-step, starting with Django 1.6.11.
There's an odd thing. There were a bunch of subclasses of a Model class, that didn't have any database fields. Django wasn't creating nor using tables for them at 1.5.12. But, Django 1.6.11 keeps trying to query these non-existent tables for these subclasses, expecting them to have a single field which would just be the pointer to their superclass. It seems the proper way to tell Django not to use tables for a class is to set: class Meta: proxy = True But if we put this in, then when we run syncdb it strangly tries to query the base classes before any tables are created at all in the database. Any old-timers run into anything like this? Did Django 1.5 not need the proxy = True in the meta to avoid creating tables for subclasses of Models that didn't add any fields? They are using InheritanceManager from django_model_utils. Thanks for any help! Banging our heads against the wall on this one for quite a while now... -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-users/45eec62d-a27c-4b5e-b8ff-6fc2981efa17n%40googlegroups.com.
