#30527: Problem with creating migrations for subclassed field changes.
-------------------------------+--------------------------------------
Reporter: Wolfgang Fehr | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: master
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 felixxm):
* status: new => closed
* resolution: => invalid
* version: 2.2 => master
* component: Core (Management commands) => Migrations
Comment:
You're use case is described in
[https://docs.djangoproject.com/en/2.2/howto/custom-model-fields/#writing-
custom-model-fields Writing custom model fields documentation]. It seems
that [https://docs.djangoproject.com/en/2.2/howto/custom-model-fields
/#field-deconstruction deconstruct()] is missing which is very important
for migrations.
Closing per TicketClosingReasons/UseSupportChannels.
--
Ticket URL: <https://code.djangoproject.com/ticket/30527#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/063.84df3b8b19f2f6601010c0df7183d397%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
