#22534: Checks fail on non-swappable ForeignKeys when the related model is
swapped
out
----------------------------+----------------------------------------
Reporter: bendavis78 | Owner: andrewgodwin
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7-beta-2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+----------------------------------------
Changes (by andrewgodwin):
* severity: Release blocker => Normal
Comment:
Your parsing of what swappable means is incorrect; it's not for a
swappable model, it's for a model that might be swapped in in place of
that model. It won't allow you to access models that are swapped out, and
that _should_ fail the checks system immediately.
I'm bumping this down from release blocker as it's just a documentation
clarification and a missing test for the false side IMO (we didn't
implement Russ' plan exactly; from what I remember, the None option wasn't
necessary in the end due to the limited options migrations had dealing
with it).
--
Ticket URL: <https://code.djangoproject.com/ticket/22534#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.d17fe5716744390209a7a1d4daaad9f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
