#35234: ExclusionConstraint.expressions should be checked for foreign
relationship
references
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: contrib.postgres | Version: 5.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> The upgrade notes or documentation does not seem to say what the
migration path is supposed to be, as just changing the code still leaves
violating code in old migrations. Are we supposed to also change old
migrations to the new syntax?
Just like with other deprecation of this form (think of
`ForeignKey(on_delete)`
[https://docs.djangoproject.com/en/5.1/releases/1.9/#foreignkey-and-
onetoonefield-on-delete-argument being made a required argument]) you have
two options
1. Squash the migration containing the old definitions
2. Edit said migrations to use the new call signature
Maybe we could adjust the release notes to include a note similar to the
`ForeignKey(on_delete)` one?
--
Ticket URL: <https://code.djangoproject.com/ticket/35234#comment:16>
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/010701929ffdc1c5-517743e9-f027-4ecc-bb5a-2500f6c6d062-000000%40eu-central-1.amazonses.com.
