#25012: Migration doesn't seem to detect foreignKey type changes
-------------------------------------+-------------------------------------
Reporter: Hedde | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution:
Keywords: postgres, | Triage Stage:
migrations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Hedde:
Old description:
> Example:
>
> {{{
> #!div style="font-size: 80%"
> {{{#!python
> class Foo(models.Model):
> id = models.AutoField() # Now change this to
> models.CharField(primary_key=True, max_length=...) and migrate, the
> migration doesn't complain
>
> class Bar(object):
> foo = models.ForeignKey(Foo) # but Postgres will still say
> Bar.foo is an Integer value.
> }}}
> }}}
New description:
Example:
{{{
#!div style="font-size: 80%"
{{{#!python
class Foo(models.Model):
id = models.AutoField() # Now change this to
models.CharField(primary_key=True, max_length=...) and migrate, the
migration doesn't complain
class Bar(object):
foo = models.ForeignKey(Foo) # but Postgres will still say
Bar.foo is an Integer value.
}}}
}}}
DataError at /myapp/bar/add/
invalid input syntax for integer: "TEST"
LINE 1: ...d") VALUES (NULL, 'TEST', ...
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25012#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/063.4989a4972579d3a0e9ae915c4325899d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
