habedi-work/useful-notes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

WIP

Browse Source
This commit is contained in:
Hassan Abedi 2026-05-13 12:54:12 +02:00
parent 6bf9d38d51
commit d6fec698fd
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
storage/001-geomerge-public-api-and-features.md
View File

@ -26,18 +26,17 @@ Native version control, large-scale concurrency, conflict resolution, general qu
## Terminology
**Geomerge**: The storage-engine prototype in this repository. It loads a compiled Geolog theory, creates tables, accepts row additions, checks laws,
and can persist and reload store state.
**Geomerge**: A storage-engine prototype for compiled Geolog theories. It loads a compiled Geolog theory, creates tables, accepts row additions,
checks laws, and can persist and reload store state.
**Geolog**: The larger database and logic system that Geomerge is intended to support. In this repo, Geolog mainly appears through compiled IR data
that Geomerge can load.
**Geolog**: The larger database and logic system that Geomerge is intended to support. Geomerge consumes compiled Geolog IR data.
**Compiled Theory**: A ready-to-load description of tables and laws. In code, this is `FlatTheory`.
**FlatTheory**: The top-level IR object Geomerge consumes. It contains a list of table definitions and a list of law definitions.
**IR**: Intermediate representation. It is the structured data format shared by `geolog-lang` and `geomerge`, rather than the source syntax a user
might write it by hand.
might write by hand.
**Path**: A stable name for a table or law, such as `Graphs`, `G.V`, or `Hom.E.foreignKeys`. Geomerge uses paths in public operations because paths
are more portable than internal table ids.
@ -189,7 +188,7 @@ Main accessors:
- `Store::dump`: debug rendering of all tables
- `Store::check_laws`: full law validation over current store contents
`Store::insert_table` is public, but the project notes indicate schema-driven table creation is the intended normal path.
`Store::insert_table` is public, but schema-driven table creation through `Store::try_from_theory` is the intended normal path.
---