What is missing
ripwire does not index SQL. A .sql file is a --skipped row with why="unsupported-ext", so stored procedures, functions, views and migrations are absent from the map, from --for, and from every navigation and change-safety command.
Why it matters
In many codebases the business logic that decides outcomes lives in stored procedures, not in the application code that calls them. When that logic is invisible:
- Routing:
--for points at the calling C#, Java or Python code instead of the procedure that holds the answer.
- Change safety:
--impact and --test-gate cannot see a change's effect across the application–database boundary.
Starting points (to be checked, not assumed)
- Grammar. DerekStride/tree-sitter-sql is MIT-licensed and actively maintained. Its coverage of procedural dialects (T-SQL, PL/pgSQL, PL/SQL, MySQL stored programs) varies, and procedures are where the value is.
- Process. Follow
prompts/add-a-language.md, starting with STEP 0: measure parse rates per dialect on public corpora before committing to anything, and report per-dialect blind spots.
- Cross-language edges. Application code usually calls procedures by name inside a string (
EXEC dbo.Foo, CALL foo(...), ORM raw queries). Linking those to SQL definitions is a second step, and it must be evidence-based and disclosed, never guessed.
A starter prompt with more detail will follow in prompts/help-wanted/.
What is missing
ripwire does not index SQL. A
.sqlfile is a--skippedrow withwhy="unsupported-ext", so stored procedures, functions, views and migrations are absent from the map, from--for, and from every navigation and change-safety command.Why it matters
In many codebases the business logic that decides outcomes lives in stored procedures, not in the application code that calls them. When that logic is invisible:
--forpoints at the calling C#, Java or Python code instead of the procedure that holds the answer.--impactand--test-gatecannot see a change's effect across the application–database boundary.Starting points (to be checked, not assumed)
prompts/add-a-language.md, starting with STEP 0: measure parse rates per dialect on public corpora before committing to anything, and report per-dialect blind spots.EXEC dbo.Foo,CALL foo(...), ORM raw queries). Linking those to SQL definitions is a second step, and it must be evidence-based and disclosed, never guessed.A starter prompt with more detail will follow in
prompts/help-wanted/.