#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: needsinfo
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 bmispelon):
* status: new => closed
* resolution: => needsinfo
Comment:
I'm also unabled to reproduce this (tried sqlite and postgres).
I did make one change compared to the models you provided: I replaced
`TimeStampedModel` with a regular `models.Model`.
So maybe the problem is in `TimeStampedModel`?
On a sidenote, compiled regexp don't implement `__eq__` in python, so two
different regexp objects will always be different, even if they use the
same `pattern` and `flags`.
I'll close this as `needsinfo`. Can you reopen with either the full
definition of `TimestampedModel` or a fully contained testcase (something
that doesn't use external models)?
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/22289#comment:10>
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/065.023c2ab8ec1d61be2aff66129010909f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
