#33953: RenameModel breaking change in 4.1 with ManyToManyField
-------------------------------------+-------------------------------------
Reporter: Timothy Thomas | Owner: Iuri de
| Silvio
Type: Bug | Status: closed
Component: Migrations | Version: 4.1
Severity: Release blocker | Resolution: fixed
Keywords: RenameModel | 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:"524ea6b77b9bcc8cb24fd0b55e5cb8ca4186ee4f" 524ea6b7]:
{{{
#!CommitTicketReference repository=""
revision="524ea6b77b9bcc8cb24fd0b55e5cb8ca4186ee4f"
[4.1.x] Refs #33953 -- Fixed test_rename_model_with_db_table_rename_m2m()
crash on SQLite < 3.20.
Backport of a9e7beb959bc726eab1c192d2625d6ff6cfa70f4 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33953#comment:10>
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/01070182e8a568bf-952a37a1-b4db-4639-a358-d6d9e26ee936-000000%40eu-central-1.amazonses.com.
