Javier > I don't see how this solves anything. At the end of the day these "real" models, or at the very least, not "fake" models will not have any custom queryset/manager/properties/ method you add to it. Can you explain what it is you're trying to accomplish?
I don't think that's the goal of the project in the first place. To me the abstract section clearly highlights why this is useful. Right now the schema editor requires access to *rendered* model classes which is quite slow as it involves dynamically creating (or recreating) Python classes and all its dependency chain on most alterations during migration application. It's way cheaper to create and alter ModelState instances (simple class instances) than creating classes hierarchy over and over again. Le lundi 23 mars 2020 17:14:04 UTC-4, Javier Buzzi a écrit : > > I don't see how this solves anything. At the end of the day these "real" > models, or at the very least, not "fake" models will not have any custom > queryset/manager/properties/method you add to it. Can you explain what it > is you're trying to accomplish? > > On Monday, March 23, 2020 at 12:59:55 PM UTC-4, Sanskar Jaiswal wrote: >> >> Hey everyone, >> >> Here is my proposal for GSoC. My project is based upon making use of >> ModelState during the migrated phase of the project, rather than rendering >> fake Models. >> >> https://gist.github.com/aryan9600/b1c2eaf445006c17e02e7677cf1098d5 >> >> Feedback and criticism is highly appreciated. >> >> Thanks! >> Kind regards >> Sanskar >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1ad19db8-37d3-4307-b8d4-aecd9b6fd105%40googlegroups.com.
