#14615: Related objects manager returns related objects with null FKs for
unsaved
instances
-------------------------------------+-------------------------------------
Reporter: tonnzor | Owner:
Type: Bug | Status: reopened
Component: Database layer | Version: 1.2
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by lukeplant):
* stage: Ready for checkin => Design decision needed
Comment:
I don't think this is ready for checkin, because we never came to a
conclusion about Carl's comments here:
https://groups.google.com/forum/#!msg/django-
developers/HP23HEfpvCE/EWVK317NkVAJ
So we are still on DDN really, because the two alternatives seem to be:
1) Use instance._state.adding to detect 'unset' primary keys
(controversial)
2) Admit that we can't cope with this situation, and call the bug a
developer error in which they get a silly answer because they've asked a
silly question.
--
Ticket URL: <https://code.djangoproject.com/ticket/14615#comment:13>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
