#470: Add Field.db_default for defining database defaults
-------------------------------------+-------------------------------------
Reporter: jws | Owner: John
| Whitlock
Type: New feature | Status: assigned
Component: Database layer | Version:
(models, ORM) |
Severity: normal | Resolution:
Keywords: sql schema | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Sanders):
Looks like Lily's opened a new PR with their newly rebased branch 🎉
Default + generated columns are in my top 10 list of wanted features for
Django.
I wanted to just add my 2¢ worth to anyone interested:
If we look at supporting returning values from inserts (with RETURNING in
pg and who knows what mechanism for other dbs) … could we also consider
leaving the design "open" to possibly accommodate generated columns from
both inserts **and** updates? 😊
--
Ticket URL: <https://code.djangoproject.com/ticket/470#comment:55>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018370399a63-c51ac82e-ea17-4328-bde6-1b68475eed99-000000%40eu-central-1.amazonses.com.
