You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this on version 0.8.3 (latest release, AFAIK).
Code in debug_toolbar/views.py, lines 81-87 (88-94 on master/trunk as I write this) executes an "explain" command with explain query plan %s for sqlite and explain %s for anything else.
For Oracle something a little more involved is required. First, the command syntax is explain plan for %s; second, the command does not in fact give the explanation as output but stores it in a table from which one needs to extract it. See http://www.orafaq.com/wiki/Explain_Plan
Thanks,
Shai.
The text was updated successfully, but these errors were encountered:
@jezdez I could provide a patch maybe but it seems we won't be able to test this on travis. Do you think that being a tool for django, and since django does supports oracle DBs, then DT should also support them even if the CI tool used doesn't? Of course this might sound better than it actually is in practice :/ What do you think?
Hi,
I found this on version 0.8.3 (latest release, AFAIK).
Code in debug_toolbar/views.py, lines 81-87 (88-94 on master/trunk as I write this) executes an "explain" command with
explain query plan %s
for sqlite andexplain %s
for anything else.For Oracle something a little more involved is required. First, the command syntax is
explain plan for %s
; second, the command does not in fact give the explanation as output but stores it in a table from which one needs to extract it. See http://www.orafaq.com/wiki/Explain_PlanThanks,
Shai.
The text was updated successfully, but these errors were encountered: