Jack Tregurtha
Jack Tregurtha
Getting this on the latest ddtrace myself (`1.4.0`). It's not clear if the issue is due to this package, however, has anyone figured out what is the cause of this?
This sounds like something you could solve with Django features relating to multiple DBs: https://docs.djangoproject.com/en/4.2/topics/db/multi-db/
I was able to verify myself this is indeed a limitation. I agree the change should be made to avoid modifying existing behavior. I also decided it shouldn't restrict behavior...