diff options
| author | Marcos Magueta <maguetamarcos@gmail.com> | 2026-05-18 12:35:26 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-05-18 12:35:26 -0300 |
| commit | cf0fffed43d0ca7618cd0013411151e057b7a32a (patch) | |
| tree | 35915aee3f7160b9ff6b41c3c0502b34050f642c /docs | |
| parent | e3d3e20dfea253de291d5b31059cd55c0eaabf02 (diff) | |
| download | Sakura-cf0fffed43d0ca7618cd0013411151e057b7a32a.tar.gz Sakura-cf0fffed43d0ca7618cd0013411151e057b7a32a.zip | |
RNT interface
Co-authored-by: Estevan Castilho <tevo@riajuu.net>
Diffstat (limited to '')
| -rw-r--r-- | docs/icl-quantification.org | 4 | ||||
| -rw-r--r-- | docs/n-way-binding.org | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/icl-quantification.org b/docs/icl-quantification.org index 7a81551..0a3ba90 100644 --- a/docs/icl-quantification.org +++ b/docs/icl-quantification.org @@ -101,8 +101,8 @@ Generator-based relations with no tree return ~Some []~. The materialisation path: 1. ~Merkle.keys tree~ — loads all tuple hashes. -2. For each hash: ~Storage.load_raw~ → ~Storable.Tuple.of_bytes~ → attribute hash list. -3. For each attribute hash: ~Storage.load_raw~ → ~Marshal.from_bytes~. +2. For each hash: ~Storage.load_raw~ -> ~Storable.Tuple.of_bytes~ -> attribute hash list. +3. For each attribute hash: ~Storage.load_raw~ -> ~Marshal.from_bytes~. This eagerly materialises the *entire* quantifier relation into memory before evaluation begins. For a relation of cardinality /n/ with /k/ attributes each, diff --git a/docs/n-way-binding.org b/docs/n-way-binding.org index 85dc0e3..c49d2a1 100644 --- a/docs/n-way-binding.org +++ b/docs/n-way-binding.org @@ -75,7 +75,7 @@ to fire when suites referencing its rooms are inserted. * ICL — Constraints Binary FK constraints compose to enforce referential integrity along the chain -~Suite → Room → Building~. Each link is declared independently. +~Suite -> Room -> Building~. Each link is declared independently. #+begin_src lisp ;; FK: every Room must belong to an existing Building @@ -140,7 +140,7 @@ However, some constraints require joining through intermediate variables before membership check can be made. These cannot be decomposed. Example: /a suite is only valid if its room belongs to a building with more than 3 floors/. -The chain ~suite.room_id → room.building_id → building.floors~ requires two intermediate +The chain ~suite.room_id -> room.building_id -> building.floors~ requires two intermediate variables — it is inherently a 3-wise constraint. Each ~Exists~ record field must be wrapped by name when written in s-expression form, as |