#20348: Consistently handle `Promise` objects assigned to model fields.
-------------------------------------+-------------------------------------
Reporter: mrmachine | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Unreviewed => Ready for checkin
Comment:
I like this. This means that lazy values are always evaluated at the time
they are needed by the DB and one can customize the way the promise object
is evaluated per field.
Ill mark this as ready for checkin. The issues keeping me from committing
this straight ahead:
- Is this too risky to commit in alpha stage?
- Could this lead to incompatibilities for custom fields?
- It seems get_prep_lookup() doesn't always use get_prep_value(). I
wonder if this could be fixed...
But, like the "ready for checkin" triage stage indicates I don't see any
of the above as blockers for commit. Waiting a bit to see if any other
opinions arise.
--
Ticket URL: <https://code.djangoproject.com/ticket/20348#comment:3>
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/067.c46209b3dca2b5aa10f835e0148bb7ab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
