#31206: Migration crashes when altering a field to use the db_returning flag and
default value returned from database.
-------------------------------------+-------------------------------------
Reporter: Tom Kazimiers | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* cc: Johannes Hoppe (added)
* stage: Unreviewed => Accepted
Comment:
Thanks for this ticket, we should fix
[https://github.com/django/django/blob/5d654e1e7104d2ce86ec1b9fe52865a7dca4b4be/django/db/backends/base/schema.py#L671-L686
handling "effective" defaults] in such cases. It's not a release blocker
because `db_returning` is still a part of undocumented and private API.
--
Ticket URL: <https://code.djangoproject.com/ticket/31206#comment:1>
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/063.d9b2f5aeff926663df17f3af8940057b%40djangoproject.com.
