#35022: migration fails from index_together to models.Index
-----------------------------------+--------------------------------------
Reporter: Thomas Capricelli | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 5.0
Severity: Normal | Resolution: worksforme
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 Natalia Bidart):
* status: new => closed
* resolution: => worksforme
Comment:
Hello, thank you for your report.
I have tried to reproduce this with a minimal example using the data you
showed above, but I can't reproduce (I used Django 4.2 since that's the
version where the deprecation started, and I also tested on Django 5.0).
Questions:
1. Did you modified your models.py, generated the migration and migrated
using the same Django version? If yes, which one?
2. You refer to a `unique_together` index which you haven't provided any
details for, could you please share minimal but complete models.py to
reproduce the issue?
Lastly, if you are unsure about whether your models are doing the right
thing or not, you could also seek assistance from one of the Django
support channels where there are many friendly people that can help you:
https://www.djangoproject.com/community/
Closing as `worksforme` for now, until further details are provided.
--
Ticket URL: <https://code.djangoproject.com/ticket/35022#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/0107018c400a76c0-a21195a2-badc-40b9-9757-426f41ccc5d8-000000%40eu-central-1.amazonses.com.
