--
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-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3509e4d0-e99c-4ff3-a4d0-45a5c3a988e3%40googlegroups.com.
--
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-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8e9a5959-d677-456f-9bb8-953e68162562%40googlegroups.com.
Hey SimonJust so that I am more clear, is it favourable to move all logic that ModelOperations and FieldOperations implement right now to ProjectState and ModelState?Kind regardsSanskar
On Tue, 24 Mar 2020 at 04:20, Sanskar Jaiswal <jaiswal....@gmail.com> wrote:
Hey Simon,
Thank you for your feedback! It helps a lot. I shall look into your doubts right now, and edit my proposal accordingly.
Kind regards
Sanskar
On Tue, Mar 24, 2020 at 3:37 AM charettes <char...@gmail.com> wrote:
--Hello Sanskar,Thank you for your submission, from a quick look it seems to be heading in the right direction.Would it be possible to break the large overview section into more granular sections where you describe how you roughly plan to tackle each of the point mention?I personally have doubts about your desire to make minimal change to the schema editor and offload the logic to database_forwards instead of the other way around. That doesn't seem to be in line with a future deprecation of support for direct model passing. I'd much rather see us move all methods to (project_state, model_state, *other_state, **other_fields_and_flags) signatures and provide helpers to help third-party backends migrate (e.g. a method decorator that renders mode) then embedding logic for both paths in the schema editor and adding schema specific logic to Operation.database_forwards.Simon
Le lundi 23 mars 2020 12:59:55 UTC-4, Sanskar Jaiswal a écrit :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.Feedback and criticism is highly appreciated.Thanks!Kind regardsSanskar
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-d...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fbf6ba88-2adc-4dd7-ac82-ecea6d1be313%40googlegroups.com.
Hey Simon
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fbf6ba88-2adc-4dd7-ac82-ecea6d1be313%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3b9516a5-3c0e-4707-b142-1eb8e091168b%40googlegroups.com.
Hi SimonTaking advice into account, I have made some more changes to my proposal. Please check it out and criticize it wherever you think I could improve it as always. :)
Also, could you kindly give some kind of idea as to when the new mappings should be populated? I think it makes sense to do so whenever we run makemigrations. Do you have a better idea?
Thanks!Kind Regards
Sanskar
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3b9516a5-3c0e-4707-b142-1eb8e091168b%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/668c02b4-8a27-43fd-b449-53121d8e3a73%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CACzaa%3DEn1uS9dwv4A%2Bbj9c4y4o4%2BWG0y3NCBNsZb_nAbYJFfMQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALzH9que%3Dp0XoFwo0oXu6ogJ%2B7df9pNFShM0D0%3D3RWRbGkx8ZQ%40mail.gmail.com.
Hey Simon,
While I certainly see the benefits of this, I still fail to understand how this would help ModelState get access to related db_types, (the problem that the mapping in my proposal aims to solve). Am I missing something here? Some more clarification/explanation would be highly helpful.
Kind regards
Sanskar
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/668c02b4-8a27-43fd-b449-53121d8e3a73%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b4628e57-95e8-4390-be21-5ba5b2bf2f8d%40googlegroups.com.