#33366: Foreign key to settings.AUTH_USER_MODEL causes hard-coded alteration in
migration
-------------------------------------+-------------------------------------
Reporter: Andrew | Owner: nobody
Chen Wang |
Type: Bug | Status: new
Component: Database | Version: 4.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
We have a model in a package called [django-oauth-
toolkit](https://github.com/jazzband/django-oauth-
toolkit/blob/0204383f7b6f8739322f2009f2bb25e8ac9bced2/oauth2_provider/models.py#L78)
Our model for reproduction:
```
class RefreshToken(models.Model):
user = models.ForeignKey(
settings.AUTH_USER_MODEL, on_delete=models.CASCADE,
related_name="%(app_label)s_%(class)s"
)
```
Users of the package are running `makemigrations` and having to see
something like this (ref: https://github.com/jazzband/django-oauth-
toolkit/issues/1037):
```
migrations.AlterField(
model_name='refreshtoken',
name='user',
field=models.ForeignKey(on_delete=django.db.models.deletion.CASCADE,
related_name='%(app_label)s_%(class)s', to='auth.user'),
),
```
Specifically, `to='auth.user'` is the issue. Our previous migrations
properly had `to=settings.AUTH_USER_MODEL`. Please let me know how to fix
this or whether this is a bug. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/33366>
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/059.819061faa00aa4442b6549bd2fc6de5a%40djangoproject.com.
