Philipp

I can also confirm this issue, and it makes it a little bit hard to trace back errors [Here](https://github.com/encode/django-rest-framework/pull/1671) is a discussion related to this problem

I agree.

I would very much welcome this for projects where DRF is already heavily used. I am facing this now. I have defined serializers for allmost all resources, including the creation/update...

I don't know anything about the actual implementation of this library, but I've seen esupport libraries which add "DRF" capabilities to another library. One small example is django-polymorphic and django-rest-polymorphic...

> Hi @stuart-leitch, it's doesn't seems like the API method AddProjectNextItem supports such kind of functionality https://docs.github.com/en/graphql/reference/input-objects#addprojectnextiteminput > > As a workaround I can suggest to use a custom action...

Regarding the usage of `celery`, maybe this would be a nice small addition to the docs: In your apps `task.py` file, add the following: ```python from celery import shared_task from...

I can confirm this happening on SQLite, which is quite handy in development.

@duwangthefirst good idea, albeit only working if you have a single `order_with_respect_to` field. I can confirm that this _seems_ to work and is a probably an easy workaround until pull...

That sounds cool. Running a docker in development just to circumvent those issues is a pain anyway, so I will give this a try.

> Noting that a tweak to @mumumumu's workaround works for SET_NULL too (which was the problem in my case). > > ``` > def NON_POLYMORPHIC_SET_NULL(collector, field, sub_objs, using): > return...