Finn Andersen

I have made a fix to support decoding SET fields in any order, there is a pull request open

Hi @Benjalill , The .decode() method of the compiled schema will only decode the first record from the start of the byte data provided. In order to decode multiple records...

EDIT: Nevermind, I think this addresses a different issue Does this solve the problem for anyone? https://gist.github.com/Finndersen/3a9647718b35d6776b0dc3808a501519 Adds new select_polymorphic_related() Queryset method. Might look into having it handle it seamlessly...

By the way it appears doing a plain select_related() (without specifying fields) on the parent queryset works to select related instances on child classes, if this helps anyone

@AndySun25 nice one, I made some changes to support Polymorphic Proxy models: https://gist.github.com/Finndersen/3a9647718b35d6776b0dc3808a501519

PolymorphicRelatedQuerySetMixin could probably be modified to integrate select_polymorphic_related() functionality seamlessly into normal select_related()? Note my update above also supports chaining of select_polymorphic_related() (previous version would override fields in PolymorphicModelIterable with...

Just loading fixtures during standard Django TestCases, or using loaddata management command. I will need some time to try create a minimum reproducible example (will be away for the next...

I'm using cachalot 2.5.1

Note i am also using diskcache.DjangoCache backend, and updating SUPPORTED_CACHE_BACKENDS to add it in to be allowed

Still occurs with cachalot at the bottom of INSTALLED_APPS. Here's the stack trace from running a custom management command which just calls loaddata command for every fixture of every app:...