jerch

Trying to shape the transformed query with ORM syntax is not quite easy, this is the closest I got for now: ```python Foo.objects.filter(pk__in=Baz.objects.all().select_related('bar').values('bar__foo_id')) ``` which creates: ```sql SELECT "exampleapp_foo"."id", "exampleapp_foo"."name",...

Oh well, can construct the joins with `extra`: ```python >>> s=Bar.objects.all().extra(tables=['exampleapp_baz'], where=['U0.id=exampleapp_baz.bar_id']) >>> _=list(Foo.objects.filter(pk__in=s.values('foo'))) ``` leading to this sql: ```sql SELECT "exampleapp_foo"."id", "exampleapp_foo"."name", "exampleapp_foo"."bazzes" FROM "exampleapp_foo" WHERE "exampleapp_foo"."id" IN (...

Is there a reason why you want Django 2.1 support back? Note that it is already 7 months overdue. Maybe we should discuss, whether there should be an option to...

@mobiware > ... as some uses of DCF might rely on the models save() method being called to trigger some processing depending on the computed fields value. Ah good point,...

@mobiware Thinking more about the `save` invocation, I am not sure yet, whether it should be done at all. Note that field updates done by the resolver are quite special...

@mobiware For that particular case - would it be easier for you with a custom signal, that indicates, that some cfs were just updated, maybe with the affected models/records in...

@mobiware If this here is not pressing for you, I suggest we try to get the multi table thingy working first. Then we can dig into this here. My current...

@mobiware Would like to hear your ideas, how such a signal could look like. Also did some thinking/investigation on securing the sync state (related to the question, when it is...

@mobiware Plz see #56 to discuss the layout of a custom signal and/or method hooks.

@mobiware I am afraid, that a data structure shaped this way will bloat the memory for holding CF names in individual lists for every changed PK. In #58 I have...