#33194: Remaking table with unique constraint crashes on SQLite.
-------------------------------------+-------------------------------------
Reporter: Mark | Owner: Hannes
| Ljungberg
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | 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:"00aa3e0b9b8fac8fa5adab47249790d2ee2f767e" 00aa3e0b]:
{{{
#!CommitTicketReference repository=""
revision="00aa3e0b9b8fac8fa5adab47249790d2ee2f767e"
[4.0.x] Fixed #33194 -- Fixed migrations when altering a field with
functional indexes/unique constraints on SQLite.
This adjusts Expressions.rename_table_references() to only update alias
when needed.
Regression in 83fcfc9ec8610540948815e127101f1206562ead.
Co-authored-by: Simon Charette <[email protected]>
Backport of 86971c40909430a798e4e55b140004c4b1fb02ff from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33194#comment:8>
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/064.4d92a878b87b7ab9bdc8d3e2536c81df%40djangoproject.com.
