#30955: Document the different behavior of migration historical models while
they
have abstract base classes.
-------------------------------------+-------------------------------------
Reporter: Shipeng Feng | Owner: Shipeng
Type: | Feng
Cleanup/optimization | Status: closed
Component: Documentation | Version: 2.2
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"59578ebaa0bd6cd03c4c3dbfd7fdc06babce01a9" 59578eba]:
{{{
#!CommitTicketReference repository=""
revision="59578ebaa0bd6cd03c4c3dbfd7fdc06babce01a9"
[3.0.x] Fixed #30955 -- Doc'd that only concrete base models are stored in
historical models bases.
Abstract models are removed from bases when generating historical model
state since 6436f1fad9ce51f18735106ac75aeea3d6d1f310.
Backport of 8058d9d7adb189fec75a4b57565f225996c7b22c from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30955#comment:5>
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/064.7b3a726671a3d252d0c71c4d52bb0630%40djangoproject.com.
