#470: Add Field.db_default for defining database defaults
-------------------------------------+-------------------------------------
Reporter: jws | Owner: Lily
| Foote
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: normal | Resolution: fixed
Keywords: sql schema | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"836894f27a0e2c32dbbecbe8392ba7d4d0d17d8a" 836894f2]:
{{{#!CommitTicketReference repository=""
revision="836894f27a0e2c32dbbecbe8392ba7d4d0d17d8a"
Refs #470 -- Adjusted Field.db_returning to be backend agnostic.
Determining if a field is db_returning based on the default connection
feature availability prevents the usage of RETURNING for db_default
fields in setups where non-default backends do support RETURNING.
Whether or not the field should be attempted to be returned is already
checked at the compiler level which is backend aware.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/470#comment:72>
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 visit
https://groups.google.com/d/msgid/django-updates/01070198d812a585-155d5196-db47-41d4-a3f5-0cf737fb00fe-000000%40eu-central-1.amazonses.com.
