Hi A Lee, Can't say for sure but probably it is because your related_name is not unique in core/migrations/0001_initial.py (https://github.com/virtualcommons/vcweb/blob/develop/vcweb/core/migrations/0001_initial.py#L647, https://github.com/virtualcommons/vcweb/blob/develop/vcweb/core/migrations/0001_initial.py#L208) And based on django documentation the related_name must always be unique (https://docs.djangoproject.com/en/1.8/topics/db/models/#be-careful-with-related-name)
It is just an assumption. Yours sincerely, Pavel Hello, > > After upgrading to 1.8 from 1.7.7 our tests are now unable to create test > data via data migrations and complain about related collections not > existing as attributes for some but not all models (exception stack trace > at https://travis-ci.org/virtualcommons/vcweb). It appears to succeed at > creating a model object for the first related collection but then dies when > attempting to create objects in the second related collection ( > https://github.com/virtualcommons/vcweb/blob/develop/vcweb/experiment/forestry/migrations/0001_initial_forestry.py#L62 > ). > > Any ideas on what might be causing this? Access to related collections > through the django shell and via the web interface still seem to be working > fine on 1.8, it's just the data migrations that are failing. > > -- 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/7be04264-e0cb-436a-af72-b11b89da0af0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
