#32344: Allow arbitrary `deconstructible` class properties to participate in
migrations
-------------------------------------+-------------------------------------
Reporter: Ryan Vinzent | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: Migrations, | Triage Stage:
ModelState | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I think this is part of a larger discussion around #5793 so I'll close
this one as a duplicate.
The issue here is that we not only need a way to detect these changes but
also a way to keep track of them and their evolution through time. If we
were to add support for custom attributes addition like #5793 proposes
we'd get all of that for free as these ''options'' would be included in
`ModelState.options` and ultimately make their way to the schema editor.
--
Ticket URL: <https://code.djangoproject.com/ticket/32344#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.ff5f9269a9f06c27b9b4e2a1dead29eb%40djangoproject.com.
