rename feedback view to return success messages after running queries that do not return anything#275
Merged
danvergara merged 1 commit intomainfrom Oct 17, 2025
Merged
Conversation
…ning queries that do not return anything
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
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.
Add feedback page
Description
This PR introduces a new feedback view to provide users with more informative messages about the execution of their SQL queries. Previously, the UI only had an error page, which was displayed for both errors and successful queries that didn't return any rows. This could be confusing for users.
The new feedback view replaces the error page and provides the following features:
This change improves the user experience by providing clearer feedback on the query execution status.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
I have tested this feature by running the following queries:
SELECT * FROM users WHERE 1 = 0).SELECT * FROM non_existent_table).Checklist: