#31064: Migration doesn't detect precision changes in fields that ManyToMany
points
to.
-----------------------------+---------------------------------------------
Reporter: zapililirad | Owner: Simon Charette
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | 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
-----------------------------+---------------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a54828085732d5d2f020c2fb52fe1cbe1a20a6c9" a5482808]:
{{{
#!CommitTicketReference repository=""
revision="a54828085732d5d2f020c2fb52fe1cbe1a20a6c9"
Fixed #31064 -- Recreated auto-created many-to-many tables on primary key
data type change on SQLite.
Both local and remote auto-created many-to-many relationships were
affected.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31064#comment:13>
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/069.94e96bc33d4949dc15eae9f19d3ee4d8%40djangoproject.com.
