#26321: Missing "for_save" in examples of custom expression
-------------------------------+------------------------------------
Reporter: tomaszn | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: expressions | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by jarshwah):
* keywords: postgres aggregate => expressions
* stage: Unreviewed => Accepted
Comment:
I've renamed the case because this is about custom expressions, not
specifically about postgres or aggregates (which don't actually use
for_save). Patch looks mostly fine to me. Would you mind submitting it as
a PR on GitHub? That'll allow review and the automated tests to run.
--
Ticket URL: <https://code.djangoproject.com/ticket/26321#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 [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/065.960cdff8e0f6ab144b162e40e57b2d50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
