#26586: makemigrations does not detect custom field subclassing change
-------------------------------------+-------------------------------------
Reporter: tuffnatty | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: migrations, custom | Triage Stage: Accepted
fields |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by tuffnatty):
I think that expected behaviour is to generate an `ALTER TABLE table_name
ALTER COLUMN column_name TYPE TEXT` migration operation. However, I'm not
familiar enough with migration internals to predict what it takes to
detect a change like this.
--
Ticket URL: <https://code.djangoproject.com/ticket/26586#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/067.8ce399ae3b3068a953c6d93fea964536%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
