#25068: Metaclass conflict when doing createmigrations in ModelState.render
-------------------------------------+-------------------------------------
Reporter: kosz85 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: metaclass conflict | Triage Stage: Accepted
createmigrations |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by MarkusH):
I'm not really happy with bundling `metaclassmaker` either. Furthermore, I
think there are a few problems with your current implementation:
1. What happens if a model's metaclass changes from `MyModelBase` to
Django's `ModelBase` or vice versa?
1. I don't see an explicit tracking of the class in generated migration
files, do I?
1. As the metaclass has to be tracked inside migrations (only which
metaclass, what the metaclass does) but is only referenced from the
regular code base, can we find a solution like for the model managers?
1. Keep in mind, that any fields a metaclass adds to a model are
automatically serialized (see e.g. abstract models).
--
Ticket URL: <https://code.djangoproject.com/ticket/25068#comment:12>
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/064.6f38c146ab6b48f51d041586ad783e84%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
