#24509: Allow Expressions when saving new models
-------------------------------------+-------------------------------------
Reporter: AlexHill | Owner:
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
Just for future reference for whoever works on this: I spent a few minutes
looking at this tonight and I think that implementing this _might_ allow
us to get rid of the whole `Field.get_placeholder()` hook, which is
effectively just a hacky way to allow fields to wrap their values in an
arbitrary SQL expression at save time. (Currently only GIS fields use this
hook in core.)
In the meantime, if you're wishing Django 1.8 had this feature,
`get_placeholder()` appears to be a usable workaround (for any given
specific field type; doesn't offer generic support).
--
Ticket URL: <https://code.djangoproject.com/ticket/24509#comment:6>
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.56a124f6277cd21e5a0bdd30343b6439%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
