Private Preview - features may change without notice
GramSpec
Architecture Spec API Reference Pricing About
Start free

Make the model · 4

A model from a database you already have

The answer to “what if it gets the joins wrong?” Connect, pick the tables that matter, and the model is built from what the database already defines: its keys and its relationships. Where the database does not say how two tables relate, a join is proposed and waits for someone to confirm it. Nothing is guessed and carried on.

A model from a live database. The chosen tables are turned into a model by rule from their declared keys. Joins the database never declared are proposed from the data and reviewed before anything is built.GRAMSPECYOUR DATAWhoever knows thedatabasePick the tablesfrom a saved connectionStructure, by ruledeclared keys become factsJoins nobodydeclaredproposed, and checkedagainst the rowsRevieweach proposal is a tick boxThe modelbound to the connection itcame fromYour databaseread-only12345 A model from a live database. The chosen tables are turned into a model by rule from their declared keys. Joins the database never declared are proposed from the data and reviewed before anything is built.GRAMSPECYOUR DATAWhoeverknows thedatabasePick thetablesfrom a savedconnectionStructure, byruledeclared keysbecome factsJoins nobodydeclaredRevieweach proposal isa tick boxThe modelbound to theconnection itcame fromYourdatabaseread-only12345
One flow. No language model is asked at any step of it.
  1. Whoever knows the database picks the tables. From a connection already saved: its tables and views as a tree, and a tick beside each column that matters.
  2. The structure becomes a model by rule. Each table is a thing, each column a value of it, and each key and foreign key the database declares becomes a fact with its counts. It is the same result every time, and it is instant.
  3. Joins the database never declared are proposed. A warehouse often joins on a key that is only a matching column name. Those pairs are found, the rows are read to check that one side really is unique, and each survivor is graded strong, likely or possible.
  4. Someone reviews before anything is built. Every proposed join and every proposed identifier is a tick box, ordered by how sure it is. A clean import says so in a line. A proposal is never applied unasked.
  5. What was confirmed joins the model. Beside whatever is already on it, with tables brought in twice counted once. The model keeps the connection it came from, so it can be asked straight away.