Summary
When the [sql] extra is not installed, .sql files are counted as code and scanned, but silently produce 0 nodes — no warning, no error. The graph looks successfully built while the entire SQL corpus is missing.
Environment
- graphifyy 0.9.7 (pipx), Python 3.14.5, macOS (arm64)
Reproduction
pipx install graphifyy # note: no [sql] extra
graphify extract <dir-with-213-sql-files> --no-cluster
Output reports found 227 code, 0 docs, ... and writes a graph — but it contains only the non-SQL nodes (in our case a handful of TypeScript files). The per-file zero-node warning (#1666-style) listed only 2 JSON files; the 213 .sql files vanished without a trace.
After pipx install --force "graphifyy[sql]" the exact same command extracts tables, FK references and triggers correctly (single test file: 12 nodes / 35 edges).
Expected
Either a hard gate like the existing LLM-key check ("A code-only corpus needs no key") — e.g. "N .sql files need the [sql] extra: pip install 'graphifyy[sql]'" — or at minimum, the .sql files should appear in the zero-node warning list.
Impact
Users reasonably believe their database corpus is indexed when it isn't; we lost an evaluation pass to this before finding the extra by searching the README.
Summary
When the
[sql]extra is not installed,.sqlfiles are counted as code and scanned, but silently produce 0 nodes — no warning, no error. The graph looks successfully built while the entire SQL corpus is missing.Environment
Reproduction
Output reports
found 227 code, 0 docs, ...and writes a graph — but it contains only the non-SQL nodes (in our case a handful of TypeScript files). The per-file zero-node warning (#1666-style) listed only 2 JSON files; the 213.sqlfiles vanished without a trace.After
pipx install --force "graphifyy[sql]"the exact same command extracts tables, FK references and triggers correctly (single test file: 12 nodes / 35 edges).Expected
Either a hard gate like the existing LLM-key check ("A code-only corpus needs no key") — e.g. "N .sql files need the [sql] extra: pip install 'graphifyy[sql]'" — or at minimum, the .sql files should appear in the zero-node warning list.
Impact
Users reasonably believe their database corpus is indexed when it isn't; we lost an evaluation pass to this before finding the extra by searching the README.