#470: Add Field.db_default for defining database defaults
-------------------------------------+-------------------------------------
Reporter: jws | Owner: Ian Foote
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 Anders Hovmöller):
I am getting bitten by this quite a lot.
I would suggest that long term it would be a good idea to have one field
for the default value set in the database schema and one that is dynamic
and set on the Django level. Maybe `default` and `default_db` to keep
backwards compatibility, or `default_dynamic` and `default` to improve the
default.
--
Ticket URL: <https://code.djangoproject.com/ticket/470#comment:41>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.a78b19632ef0deb170d96fa8d4a2aa98%40djangoproject.com.
