Support for very long SQL queries in SQL panel #357
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By using remoteCall CSS class on the `a` tag in the panel template
it is possible to instruct DDT to load content of the HTTP request
into the new panel and put it on the front of the page.
This change allows to configure this call to be a POST request instead
of a GET, which may be desirable in case of long params.
Parameters that need to be sent should be rendered as tag
attributes of `a.remoteCall` prefixed with "data-", i.e.:
<a class="remoteCall remoteCallPost" href="..." data-var="1">...</a>
will result in sending var=1 in the POST body.
|
👍 |
|
As you can see I've just closed #347 since it very related to this pull request. Would you mind incorporating the changes made there to have a better fix? |
|
Actually closing this in favor of #347. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In response to problem stated in #269.