#27860: Changing a CharField to a ForeignKey explodes when migrating in
PostgreSQL
-------------------------------+--------------------------------------
Reporter: Daniel Quinn | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: PostgreSQL | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Tim Graham):
I couldn't reproduce a problem with these final models:
{{{
class CharPK(models.Model):
id = models.CharField(primary_key=True, max_length=128)
class MyModel(models.Model):
my_field = models.ForeignKey(CharPK, max_length=128,
on_delete=models.CASCADE)
}}}
Does "alpha.MyOtherModel" have a `CharField` primary key?
I'm not sure what the proper resolution would be here, considering that
automatically generating `RemoveField` / `AddField` would be data loss
operations.
--
Ticket URL: <https://code.djangoproject.com/ticket/27860#comment:1>
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/069.b1880f40e40c5bc7faa9cd685f988f03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
