#33413: Errors with db_collation – no propagation to foreignkeys
----------------------------+-----------------------------------------
Reporter: typonaut | Owner: David Wobrock
Type: Bug | Status: assigned
Component: Migrations | Version: 3.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
----------------------------+-----------------------------------------
Changes (by David Wobrock):
* cc: David Wobrock (added)
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
* status: new => assigned
* owner: nobody => David Wobrock
Comment:
Hi there,
I started looking into this and here is a draft PR
https://github.com/django/django/pull/15629.
Plainly adding `db_collation` and making the `ForeignKey` object aware it
through a property works when creating the Models from scratch.
However, this won't make the FK object aware of changes to the related PK
field, meaning that changing/adding/removing a `db_collation`.
From my understanding, we should add it to the `db_parameters` so that
changes to the target db_collation will be reflected on the FK field and
its constraints.
--
Ticket URL: <https://code.djangoproject.com/ticket/33413#comment:4>
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/01070180587476bc-d2dcd2e4-1ea0-4c0a-9d75-ddd1cf18cc6e-000000%40eu-central-1.amazonses.com.
