#33586: Applying RunPython backward results in ValueError when involved models
are
referenced through multiple foreign keys
-------------------------------+---------------------------------------
Reporter: Jeremy Poulin | Owner: Sarah Boyce
Type: Bug | Status: assigned
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+---------------------------------------
Changes (by Jacob Walls):
* owner: (none) => Sarah Boyce
* status: new => assigned
Comment:
I commented that branch out and got failures relating to `AlterField`
operations changing the targets of an FK. From the comment above, "Get all
relations ... as _meta.apps may change." So my understanding is that the
results are not the same in those two branches (not duplicative work).
Tentatively passing over to Djangonaut Space navigators to evaluate if a
good fit for anyone (git archeology, benchmarking, migration system).
Reiterating that #36161 was a dupe with a nice low-level diagnosis of the
symptoms of the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/33586#comment:38>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019c33a1e359-abe07522-fc04-41b1-97ce-e3410b5907f0-000000%40eu-central-1.amazonses.com.