YAML Metadata Warning:empty or missing yaml metadata in repo card

Check out the documentation for more information.

cypher4sql

Neo4j-enhanced context engineering for SQL generation.

Overview

cypher4sql uses Neo4j schema graphs to provide rich context for text-to-SQL models:

  • Semantic table retrieval via vector embeddings
  • FK statistics (fanout, cardinality, risk tags)
  • Join path finding for multi-hop queries
  • Planner hints for complex joins

Architecture

User Question
     ↓
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  Neo4j Schema Graph (cypher4sql)    β”‚
β”‚  - Vector search β†’ relevant tables  β”‚
β”‚  - FK stats β†’ join risk/hints       β”‚
β”‚  - Path finding β†’ join options      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
     ↓
Enhanced Context + FK Stats
     ↓
SQL Model β†’ Query

Usage

Training

  • FK stats for reward shaping
  • Mutation validation (Phase 3.5)
  • Context engineering for training data

Production

  • Live schema retrieval
  • Semantic table ranking
  • FK stats for query planning

FK Stats Format (v4)

Join Options:
  1. orders.customer_id -> customers.id [1:N, fk_u=0.85, n=50000, fanout=3.2, risk=MED]
  2. order_items.order_id -> orders.id [1:N, fk_u=1.00, n=150000, fanout=2.8, risk=LOW]

Safe (no-dup) joins: order_items->orders

License

MIT

Downloads last month

-

Downloads are not tracked for this model. How to track
Inference Providers NEW
This model isn't deployed by any Inference Provider. πŸ™‹ Ask for provider support