I discovered a unicode problem related to the degree symbol (°) when
running under Python 2.7 and dealt with that. It somehow fixed the
IntegrityError.
One of those things I guess
AWTEW
Mike
On 15/10/2014 9:40 AM, Mike Dewhirst wrote:
Using Django 1.6.7, in the Admin if I change the name of an object (in
this case "substance") with 1:1 relationships and click [Save as new] I
get an integrity error[1]. This was working in Django 1.5.x.
Before I put in the effort to roll back to 1.5 for proof I thought I'd
check the docs and found this with a "Changed in Django 1.6" note ...
https://docs.djangoproject.com/en/1.6/ref/models/instances/#how-django-knows-to-update-vs-insert
Does anyone have a suggestion?
The interactive traceback indicates my save() method on one of the 1:1
models (in this case "gas") is triggering the problem. See below.
Thanks for any pointers
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.
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/54410C83.7000201%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.
