#24470: Serialization of base classes is not customizable for migrations
-----------------------------+------------------------------------
Reporter: rockymeza | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by carljm):
* type: Uncategorized => New feature
* stage: Unreviewed => Accepted
Comment:
On the one hand, I think there is definitely a point where we just have to
say "auto-generated migrations are on a best-effort basis, if you're doing
complex things then you will probably have to edit the auto-generated
migrations by hand."
On the other hand, this specific feature request looks relatively elegant
and generic, and I think would probably find use cases beyond this
specific situation , so provided the implementation isn't too complex in
practice I think it's reasonable.
I've marked accepted, but if anyone with more migrations experience thinks
there are serious problems here, feel free to reverse that!
--
Ticket URL: <https://code.djangoproject.com/ticket/24470#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 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/067.e112b54d2989b6f9bb82fb2e116b82d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
