#27629: Inconsistent check of allow_relation in
ForwardManyToOneDescriptor.__set__
-------------------------------------+-------------------------------------
Reporter: Sven Coenye | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: allow_relation | Triage Stage: Accepted
ForwardManyToOneDescriptor |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Stefan R. Filipek):
I'm running into this issue as well on 1.11.7 and the latest master
branch. There's a large amount of inconsistency with this behavior that
I've run into.
General constructors, create(), get_or_create() and update_or_create()
don't call allow_relation(). Assignment of a foreign key will perform the
check, only once the object has been saved.
I've been working of a fix, but it's starting to require significant
modifications.
--
Ticket URL: <https://code.djangoproject.com/ticket/27629#comment:4>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.4f288867bd171f38fc7d53412dd520b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
