Skip to content

Feat/sql usage#1720

Open
maludb-ed wants to merge 8 commits into
Graphify-Labs:v8from
maludb:feat/sql-usage
Open

Feat/sql usage#1720
maludb-ed wants to merge 8 commits into
Graphify-Labs:v8from
maludb:feat/sql-usage

Conversation

@maludb-ed

Copy link
Copy Markdown

No description provided.

safishamsi and others added 8 commits July 6, 2026 01:41
- Trendshift badge under the logo.
- A scannable capability grid (god nodes, communities, cross-file links,
  query/path/explain, rationale/doc-refs, non-code inputs, local-first build)
  plus a one-line positioning statement, right after the hero and before install.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
New push backend targeting a MaluDb memory database
(https://github.com/maludb) via its POST /v1/graph/import endpoint:
nodes become subjects, edges become subject-verb-object statements,
EXTRACTED/INFERRED/AMBIGUOUS confidence is preserved. Upserts are
idempotent server-side — same contract as push_to_neo4j.

- push_to_maludb() in export.py: stdlib urllib only (no new
  dependency), scheme-only URL check (operator-supplied push target,
  like neo4j's bolt URI — security.validate_url would wrongly reject
  localhost/private MaluDb servers), community ids ride along.
- CLI: graphify export maludb [--push URL] [--namespace NS] [--token T];
  URL falls back to MALUDB_URL, token to MALUDB_TOKEN (F-031: keep
  secrets off argv), namespace to the project directory name.
- tests: payload/report shape, community tagging, non-http rejection.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
feat: push_to_maludb exporter + 'graphify export maludb' CLI
Graphify Phase 6 DM-3 (MaluDb cross-repo docs/DATA-MODEL-GRAPH.md).

- graphify/sql_usage.py: regex scan of the source files behind a code
  graph for SQL statements; emits INFERRED reads/writes links from the
  graph's FILE nodes to '<datamodel_ns>/<schema>.<table>' targets
  (unqualified names take --db-schema). Deliberately not a SQL parser:
  the goal is 'this file touches that table' edges.
- push_to_maludb: extra_links + options passthrough (the server's
  resolve_external option stitches targets that exist in the tenant's
  data-model graph; unknown targets are reported, not fatal).
- CLI: graphify export maludb --sql-usage --source-root DIR
  [--db-schema S] [--datamodel-ns NS].
- tests: scanner accuracy (incl. qualified malu$ names + noise
  filtering), file-node mining, payload options/extra links. 45 pass.

E2E on maludb_e2e (core 0.104.0): 357 links mined from the Python API
server's app/, 75 resolved cross-namespace (59 reads / 16 writes);
'db impact e2e.maludb_edge' now surfaces app/routers/graph.py beside
the core facade builder.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- extract_sql: tag CREATE TABLE/VIEW nodes with type and parse column
  definitions (name, type, nullability) plus pk/unique constraints into
  node metadata
- pg_introspect: fetch real catalog columns, primary keys, and unique
  indexes and attach them to table nodes, replacing the synthetic-DDL stub
- sql_evidence: helpers to detect, sanitize, and parse SQL embedded in
  application-code string literals (tables read/written, join predicates)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Replace the upstream graphify README with MaluDb-focused docs: the
graph-to-MaluDb mapping, installation from this fork, MALUDB_URL/
MALUDB_TOKEN configuration, export maludb flags, the four-step
code + data-model workflow, and troubleshooting.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants