#34946: Adding a field with default and db_default drops database level DEFAULT
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: 5.0
Severity: Release blocker | Resolution: fixed
Keywords: sql, default, | Triage Stage: Accepted
migrations |
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:"0265eaa500aa01e5328989b5cd814db7234f3777" 0265eaa5]:
{{{
#!CommitTicketReference repository=""
revision="0265eaa500aa01e5328989b5cd814db7234f3777"
[5.0.x] Fixed #34946 -- Preserved db_default on combined default field
addition.
Regression in 7414704e88d73dafbcfbb85f9bc54cb6111439d3.
Backport of 8a28e983df091d94eaba77cb82fbe3ef60a80799 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34946#comment:7>
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/0107018ba958bb72-ea8b649b-2c80-4466-8b8d-d86ff7b4e55b-000000%40eu-central-1.amazonses.com.
