#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-------------------------------------+-------------------------------------
Reporter: Glenn | Owner:
Type: Bug | anubhav9042
Component: Database layer | Status: assigned
(models, ORM) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anubhav9042):
Replying to [comment:34 altlist]:
> I was suggesting an extension to the save() API, where one could pass a
"refresh=True" option. In the meantime, using my own routine.
Raising an error and notifying that the action is wrong is better approach
than allowing the user to do wrong and correct later.
--
Ticket URL: <https://code.djangoproject.com/ticket/10811#comment:35>
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/063.19862bd898c496d7064c31779cc4664b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
