csdenboer
csdenboer
I'm also having the same issue.
I would love a solution for this as well... I have to find a solution for the relationships in my child models in order to get a reasonable performance...
I wrote a third party app that provides a (de)multiplexer for Channels 2: https://github.com/csdenboer/channels-demultiplexer. Is it OK if I create a PR that adds a link to this package to...
I have created a PR (https://github.com/django/channels/pull/1503) that adds documentation about the current multiplexing support of Channels 2 and a package I have published that provides a (de)multiplexer for ``AsyncJsonWebsocketConsumer`` consumers....
You cannot use IAM roles as authentication method with django-ses (because boto does not support AWS_SESSION_TOKEN), so you cannot use with e.g. AWS Lambda.
It would indeed to be nice to make separate mixins for update and delete (both for 'semantic' and functional reasons), not an UPDATEModelMixin that also deletes relations.
I'm having the same issue...
> For nested Serializers, you'll probably want to set `exclude = (parent,)` on the child `Meta` so as not to require it. Serializers should be re-usable stand-alone and nested.
I'm running into this issue with the latest version of go-debug and a dump generated by go 1.21: https://github.com/golang/go/issues/33661