graphify v0.6.0 — SQL support: map your entire backend in one graph #640
safishamsi
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
graphify v0.6.0 is out
The big one for backend engineers.
SQL AST extraction
SQL files are now extracted deterministically via tree-sitter — no LLM, no tokens.
graphify maps:
CREATE TABLE→ table nodesCREATE VIEW→ view nodesCREATE FUNCTION/CREATE PROCEDURE→ function nodesREFERENCESconstraints → foreign key edgesFROM/JOINclauses →reads_fromedgesYour application code and your database schema are now in one graph. A FastAPI route that calls a PostgreSQL function that reads from a users table — that chain is visible. No more invisible backend logic.
Supports standard SQL, PostgreSQL, Snowflake, and any dialect tree-sitter-sql covers. Jinja-templated SQL (dbt, internal tooling) falls back gracefully.
YAML indexing
.yamland.ymlfiles are now indexed for semantic extraction automatically. Kubernetes manifests, Kustomize, Helm values, any config YAML — no setup needed.What this unlocks
For the first time you can graph an entire backend stack in one run:
.sqlfiles).yaml— k8s, docker-compose, Helm).md,.pdf)All in one graph. One query to understand the whole system.
Also in this release cycle
pip install 'graphifyy[kimi]'+MOONSHOT_API_KEYfor 3x cheaper semantic extractiongraphify updateremembers your scan rootFull changelog: https://github.com/safishamsi/graphify/blob/v6/CHANGELOG.md
Release notes: https://github.com/safishamsi/graphify/releases/tag/v0.6.0
As always — if you hit issues, open one. If you build something cool with it, share it here.
Beta Was this translation helpful? Give feedback.
All reactions