#25160: Move unsaved model instance assignment check to model.save()
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: 1.8
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
As proposed in the last comments of #10811, some people wish to use the
ORM with unsaved model instances so it's been proposed to move the data
loss check to the `model.save()` method. Such a solution would require
additional consideration for `bulk_create()` since `save()` isn't called
in that scenario. I've attached an initial patch to give an idea of the
changes required.
--
Ticket URL: <https://code.djangoproject.com/ticket/25160>
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/052.2d77293098a12a704a87f0d92e0e18de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
