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
The SQL Explain functionality breaks if there is an extremely long SQL statement via the following:
/debug/sql_explain/
Most web servers will return "414 Request-URI Too Large", and increasing this may not be acceptable in all circumstances (web app servers also require an increase if this is done).
Is it possible to make this POST rather than 'GET'?
On a side note, the query contained "hash" comments, so when copying the query out into a string, it was unusable due as it gets merged into a single line and the hash comments broke it (not even Navicat beautify was able to clean it up).
Would it be a good idea to include a little button for 'raw sql'? (shown as a <pre format with CRLF or something).
If both of these would be accepted into the core, I'd be happy to contribute.
The text was updated successfully, but these errors were encountered:
Hi,
The SQL Explain functionality breaks if there is an extremely long SQL statement via the following:
/debug/sql_explain/
Most web servers will return "414 Request-URI Too Large", and increasing this may not be acceptable in all circumstances (web app servers also require an increase if this is done).
Is it possible to make this POST rather than 'GET'?
On a side note, the query contained "hash" comments, so when copying the query out into a string, it was unusable due as it gets merged into a single line and the hash comments broke it (not even Navicat beautify was able to clean it up).
Would it be a good idea to include a little button for 'raw sql'? (shown as a <pre format with CRLF or something).
If both of these would be accepted into the core, I'd be happy to contribute.
The text was updated successfully, but these errors were encountered: