MyJackfruit

Help
Browse topics · For developers

For developers

← For developers

Why is the graph not a table?

Short answer

Records are joined by named links into a graph, with no table for each type, so a record holds only the fields it has.

Before you start

Words used here (2)
record
A record is one piece of data with its own address, such as a person, a place, a thing or a note.
field
A field is one named fact on a record, such as its title or a due date; its name comes from GilbVeda.
Deeper

Also asked:

Can I query with SQL, GraphQL or SPARQL? No. A program never sends SQL, and GilbPlatform has no GraphQL or SPARQL endpoint: lists, searches and links are asked for by address over HTTP.

A record is one piece of data with its own address, such as a person, a place, a thing or a note. In a database made of tables, each kind of thing gets a table with fixed columns, and a link is a column that holds the key of a row in another table. GilbPlatform keeps no table for each kind of thing. A record has a type and carries only the fields it has, each a fact whose name comes from GilbVeda, the shared list of terms. A record of a new type, or one with a field no other record of its type has, needs no new table and no change to the database: the type and the field are terms in GilbVeda.

Records are joined by relations. A relation is a named link between two records, such as part-of or connected-to, that says how they are related. GilbPlatform gives each link an address of its own, as it does a record: a relation is a record of its own, which names its members, each with a role, such as role:source, and has its own history. Two links of the same kind between the same two records stay two. Together the records and the links make a graph, a web of records and lines. A program asks for a record's links by adding /relations to its address; the answer on reading relations between records shows how.

Why: because every name comes from the same list, every app reads a record the same way, and a fact or a link one app adds shows up in another without a new table in either. Because a link is a record, it can be read and ended like one. And because GilbPlatform never writes over a fact, every earlier state of a record and of a link is kept.

Underneath, GilbPlatform stores all of it in PostgreSQL, a widely used database program, in a few tables that hold facts, not one per type. Apps read and write records through GilbPlatform, over HTTP, not in that database: a program never sends SQL. Lists, searches and links are asked for by address; the answers on listing records, on searching and on reading relations between records show how. The answer on what a fact, a datom, is shows how a record is stored.

A program that needs rows and columns can still have them: a view shows records as a table; the answer on rendering a view and editing its cells shows how. In GilbApp, the answer on seeing how records are connected shows the graph on screen.

The full reference is the Developer Guide, GilbPlatform's guide for people who build apps on it, in its chapter Dev.Guide.Overview, https://appbuilder.gilb.com/base/e/06gkzpwebxv8ncqr4qd7egmt58. It can be read with no sign-in, as data for programs and AIs rather than as a web page.

Source: GilbPlatform 498d29a0 (live at https://id.gilb.com/version, read 2026-11-11; code read at 498d29a0): docs/BASE-DEVELOPER-GUIDE.md §1 :2215-2224 (team notes, not linked: "One stored primitive — a bitemporal datom ... There is no per-type table and no projection table: entity documents are computed on read"; Reified relations as URIs — a relation is just an entity at /base/r/<id>; PostgreSQL 18 the primary substrate), §7.1 :7222-7241 (five tables: txns, values, facts, entity_state, relation_members (relation, role, member); compute-on-read); src/routes/read.ts (GET <record>/relations); src/lws/routes.ts (the /lws list and the vault-targeted reads). Dev.Guide.Overview (A 06gkzpwebxv8ncqr4qd7egmt58, pack GilbPlatformDeveloperGuide, 2026-11-11; read for agreement, not copied) Records (A record is one thing in a vault ... an id, a type, and facts), History, Vocabulary, Surfaces (HTTP surfaces /lws, /files, /base). Capability row note (Concepts.GraphNotTables, Agent.Architect 2026-10-28): "An answer must not say there is no SQL: the store is PostgreSQL 18 ... a developer never writes SQL to it". Row: Concepts.GraphNotTables.

Checked against GilbApp d529620.