fix(sql): use AST-based statement type detection for isSelectQuery#113
Open
fix(sql): use AST-based statement type detection for isSelectQuery#113
Conversation
The previous regex `/select/i` (no anchor) matched SELECT anywhere in the query, causing UPDATE/INSERT/DELETE queries with SELECT subqueries to be misidentified as SELECT queries. This sent them into the optimization pipeline where they'd hit EXPLAIN errors. Now uses `analysis.statementType` from @query-doctor/core when available (AST-based, handles CTEs correctly). Falls back to an anchored regex `/^\s*select/i` for skipped queries (>50KB). Requires @query-doctor/core >= 0.8.1 (adds statementType to AnalysisResult). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Query Doctor Analysis
83 queries analyzed
2 pre-existing issues
SELECT "guests"."id", "guests"."session_id", "guests"."username", "guests"."avatar_path", "guests"."color", "guests"."side", "guests"."audio_recording_path", "guests"."audio_recording_public", "gue...
indexassets(event_id, inserted_at desc)
cost 31,003,449 → 1,493 (100% reduction)SELECT * FROM guest_ip_addresses WHERE ip_address = '127.0.0.1';
indexguest_ip_addresses(ip_address)
cost 154,402 → 8 (100% reduction)
Using assumed statistics (10000000 rows/table). For better results, sync production stats.
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.
Summary
analysis.statementTypefrom@query-doctor/core(AST-based) to determineisSelectQueryinstead of the regex/select/iSELECTanywhere in the query, misclassifying UPDATE/INSERT/DELETE queries that contain SELECT subqueries (e.g.UPDATE ... FROM (SELECT ...))^\s*selectfor skipped queries (>50KB) where analysis is not availableanalyze()-based detectionDependencies
Requires
@query-doctor/core>= 0.8.1 which addsstatementType: StatementTypetoAnalysisResult. Companion PR: Query-Doctor/Site#2710.Why the regex existed
CTE queries like
WITH cte AS (...) SELECT ...start withWITH, notSELECT. The non-anchored regex was likely intended to catch those. The AST-based approach handles CTEs correctly because the parser identifies the outermost statement type (SelectStmtforWITH ... SELECT,UpdateStmtforWITH ... UPDATE).Test plan
isSelectQuerytests still pass (SELECT, INSERT, UPDATE, DELETE)analyze()integration tests verify AST-based detection for CTE, UPDATE+subquery, INSERT...SELECT, DELETE+EXISTS🤖 Generated with Claude Code