feat: add functionality to run single SQL statement at cursor (g+s)#89
Merged
Conversation
Repository owner
deleted a comment from
PeterAdams-ecitsolutions
Jan 31, 2026
Owner
|
Nice! Thanks. I found it confusing that blank lines didn't separate SQL statements. So if were to do Select 2 from Y" And have cursor on line 1, both queries would run. Other than some duplicate code, great work. Good stuff, I'm patching the PR. |
_get_statement_ranges() now handles blank-line separated statements, matching the behavior of split_statements(). Previously, g+s would run the entire buffer when statements were separated by blank lines instead of semicolons.
The quote-tracking state machine was duplicated 5 times. Now uses a single _iter_sql_chars() generator that handles escape sequences and string literal detection, reducing the file by ~100 lines.
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
2 participants
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.
What
Adds functionality to execute only the statement at the cursor position using g+s in Normal mode. Includes semicolon-aware parsing logic and unit tests.
Why
I often work on complex queries with multiple CTEs. In my workflow it is quite useful to run separately sections of the full query for testing or just prototype on the side a subquery before integrating it. In those cases, I have each query separated by ";" so that I can run them one by one in any arbitrary order. This is the main reason why I integrated this feature. I decided to reuse the "g" menu which already existed and only integrate a single option inside the
executegroup.How
Here is a high level breakdown of the main changes:
I added two new functions to handle the "single statement" detection:
_get_statement_ranges: This tracks the exact character start and end positions for every SQL statement in the editor. It should ignore semicolons inside strings. It supports semicolon-delimited queries.find_statement_at_cursor: This takes current cursor's (row, col) position, converts it to a character offset, and finds which statement range encompasses that offset.The actual execution logic:
action_execute_single_statement: This method fetches the current text and cursor location, calls the parsing logic to find the specific statement, and then executes the query in the same way as in_execute_query_common.