#470: [patch] "default" values should be expressed in SQL schema
-------------------------------------+-------------------------------------
Reporter: jws | Owner: nobody
Type: enhancement | Status: closed
Component: Database layer | Version:
(models, ORM) |
Severity: normal | Resolution: wontfix
Keywords: sql schema | Triage Stage: Design
| decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marcin Nowak):
Please reopen it and implement using INSERT ... RETURNING (for postgres).
This may be optional behaviour dependent on db engine used.
Defaults computed at the database level are very important. This may be
optional feature, but it should be available. The database is most
important and long-lived part of any bigger system.
Python-like callbacks passed as defaults shouldn't be supported, of
course. They may behave same as before and they should not be listed in
RETURNING clause.
--
Ticket URL: <https://code.djangoproject.com/ticket/470#comment:16>
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/061.41c64ec89df3c72102a795b30da071d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
