#27419: Model that worked before 1.10 causes "Cannot force an update in save()
with
no primary key." in 1.10.
-------------------------------------+-------------------------------------
Reporter: Louis-Dominique | Owner: nobody
Dubeau |
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: save model property | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Lucas Moeskops):
* status: new => closed
* resolution: => needsinfo
Comment:
It seems to have to do with specifying a different name attribute ('b') on
the field than the field name itself ('_b'). If I omit that attribute, the
tests pass. I can't find documentation for passing a different `name`
attribute. Maybe this is incorrect?
--
Ticket URL: <https://code.djangoproject.com/ticket/27419#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.bd83e282cc65719d2e567e98beb87c80%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
