Restore typing-time column-typo hint for SQL expressions via known-function list #16
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The function-call validator fix removed
invalid_ident_at_cursor's "No such column" flag atsql_expr_identpositions — necessary to stop the false positive on function names likesum, but it cost the typing-time signal for genuine column typos in incomplete SQL expressions (e.g. typingselect Agxbefore addingFROM).What still works
pick_hint_diagnosticsurfaces"no such column: Agx". So the typo is visible at typing time for any expression-with-scope.What this ticket would restore
A curated known-function list. Then at
sql_expr_identpositions the check can stay strict: flag the partial as "no such column" only if it doesn't prefix-match any known function name AND doesn't prefix-match any schema column. That gets the early-warning signal back without re-introducing the false positive.Scope to settle
Related
genuine_column_typo_in_complete_select_still_hints_via_diagnosticpins what does still work; this ticket closes the gap for incomplete inputs.Resolved by ADR-0022 Amendment 6 (commit
6d8c9ee): the typing-time column-typo hint is restored for SQL expressions — invalid_ident_at_cursor bails only when the partial prefix-matches a known function, else falls through to the schema-column check (soselect Agxwarns,select sumdoes not). See docs/handoff/20260602-handoff-53.md.