#22534: Checks fail on non-swappable ForeignKeys when the related model is
swapped
out
---------------------------------+--------------------------------------
Reporter: bendavis78 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by bendavis78):
For reference, the swappable keyword was originally proposed here:
https://groups.google.com/forum/#!msg/django-
developers/arSS604xc6U/24j1vKtlESoJ
Although, it was not implemented as proposed. Russel suggested that the
`swappable` keyword default to `None`, as we can safely assume that when
the "to" model is not a string, it should point to the original. If `to`
is a string that points to a swappable model, we would assume that it
should point to the swapped model. Any other case would be an edge case,
and can be controlled explicitly by setting the keyword to either `True`
or `False`.
--
Ticket URL: <https://code.djangoproject.com/ticket/22534#comment:2>
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.8afe74510dcc1fca347fa1fc98463aea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
