On 18/10/2015 6:28 AM, Tim Graham wrote:
Do you have code that worked before (didn't result in data loss) but
doesn't work now? If so, it could be a bug in Django.
Yes indeed. It is all in my repo. I'll go back to 1.7.x and rerun the
tests and report back.
Thanks
Mike
On Friday, October 16, 2015 at 8:30:07 PM UTC-4, Mike Dewhirst wrote:
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 django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto: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/a96af71f-3ad2-4789-9c91-c297f5cf4f89%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/a96af71f-3ad2-4789-9c91-c297f5cf4f89%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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/562339A3.2010603%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.
