#20988: Model.save() refactoring incompatibilities
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Release blocker | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Currently adding "select_on_save" flag is the favoured approach. This is
discussed at https://groups.google.com/forum/#!topic/django-
developers/coQ19f1VhTk.
There are pull requests for 1.6 and master for this at
https://github.com/django/django/pull/1522 and
https://github.com/django/django/pull/1523. They should be pretty much
ready-for-checkin at the moment.
I will wait for more feedback for some time. Unless objections are risen I
will commit this one by the end of this week.
--
Ticket URL: <https://code.djangoproject.com/ticket/20988#comment:2>
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/066.711f4870eeacc0f45679fbbdaa945923%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
