Ticket claims this is fixed, but as I've moved my project to Django 1.7, I've seen story from OP's mail repeat. My migrations create tables, then populate them with data. Then tests that read this data from DB blurp with "DoesNotExist".
> Any initial data loaded in migrations will only be available in TestCase > tests and not in TransactionTestCase tests, and additionally only on backends where transactions are supported (the most important exception being MyISAM). My tests inherit from TestCase and are ran against @PostgreSQL 9.3 which according to doc should support migrations data. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7e071bc2-c563-439a-9f8f-88e24d150945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
