#22289: Field with Validator always considered changed in migrations
----------------------------+---------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7-alpha-2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------
Changes (by erikr):
* status: new => closed
* resolution: => invalid
Comment:
I don't think this is a bug in Django. In current master, there is no
command `schemamigration --auto`, there is only `makemigrations`. When I
test a fresh project with your model, using the new built-in schema
migrations, I can not reproduce this issue - it consistently works
correctly. Therefore, this may be a bug in South (which implements
`schemamigration --auto`, but does not appear to be one in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/22289#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.21a82f99fb127c659d3fb99f46cdba98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
