#35635: Adding a field with a default in migrations following an index rename
seems
to fail
-------------------------------------+-------------------------------------
Reporter: Raphael Gaschignard | Owner: (none)
Type: Bug | Status: closed
Component: Migrations | Version: 5.0
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Sanders):
* resolution: => needsinfo
* status: new => closed
Comment:
Hi & thanks for the report.
Although I observed the exception on the branch you've linked, I couldn't
reproduce this with a simple example following the steps provided.
My advice would be to reproduce this either with the simplest setup
possible or through a unit test then paste the details here 👍
Closing with needsinfo for now until more info or someone with more time
can investigate and confirm the presence of a bug with Django,
--
Ticket URL: <https://code.djangoproject.com/ticket/35635#comment:2>
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/01070190f8ee6253-cd2519d8-dedf-45a9-85bb-8f3356480d07-000000%40eu-central-1.amazonses.com.
