I think I understand this error and I like what it does. My question is ...
What is the necessary coding paradigm when you have all sorts of m:1, 1:m and m:m relationships and need to create those objects when they don't exist when saving a new central object?
I'm moving from 1.7.x to 1.8.5 and this error seems like a show-stopper at the moment.
Thanks Mike -- 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 [email protected]. To post to this group, send email to [email protected]. 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/56219660.2030006%40dewhirst.com.au. For more options, visit https://groups.google.com/d/optout.
