Matthias Kestenholz

Nobody took the time to submit a pull request until now, so there's no update yet, unfortunately :-/

We could go the 3. route while keeping at least one unit test and it would probably be fine (we would be warned soon when the code is changed or...

I'm going to close this issue with the same reasoning as provided here: https://github.com/jazzband/django-debug-toolbar/issues/1591#issuecomment-1062618510 Feel free to reopen if you disagree. Thank you!

This may be because Django ensures that all database connections are cursors differ between threads. I think it may be very hard to implement cross-thread tracking of queries; there probably...

I think this is a duplicate of #907

@Caiofcas Thank you! If I'm reading this issue correctly it is about the whole SQL string being bytes which is different from the test where (only) a parameter is bytes.

@Lucidiot It seems nobody is actively working on this right now. Does the proposed fix in the initial report make everything work as it should? It would be very helpful...

The debug toolbar has a history panel since 3.0 which allows switching to old requests and viewing their data. So therefore I'm going to close this as completed.

I'm going to close this issue with the same reasoning as provided here: https://github.com/jazzband/django-debug-toolbar/issues/1591#issuecomment-1062618510 Feel free to reopen if you disagree, or contribute in a different area. Thank you!

Hey That's interesting. I didn't even know about `ArraySubquery`. The basic problem is that django-tree-queries is a bit of a hack (a well working hack, but still a hack) which...