ores.sql

Table of Contents

This page is the node for the ores.sql technical space in the codegen physical-space address graph. Its title is its MASD address; it gathers the facets generated for this technical space. Each facet is its own document, linked from the table below. Codegen traverses this graph (root → technical space → facet → archetype) to resolve which archetypes an entity generates.

Summary

The SQL projection of the system: DDL for entity and junction tables (ores.sql.schema), IAM artefacts from the service registry (ores.sql.service), and reference-data INSERTs (ores.sql.populate). Schema and service facets are profile-driven with outputs under projects/ores.sql/; the populate family is invoked directly by generator.py's dataset pipeline.

Shared conventions

  • {{{sql_license}}} triple-stache injects the SQL licence header verbatim; many templates also keep a pre-literate {{! purpose }} comment and an AUTO-GENERATED SQL banner.
  • Column/list loops use {{^last}},{{/last}} inverted sections for comma placement.
  • File naming follows {component}_{entity_plural}_<verb>.sql under projects/ores.sql/create|drop|populate/.

Facets

Facets in this technical space — each links to its own node doc. Generated; do not edit by hand.

Facet Archetypes Description
ores.sql.populate 9 Reference-data population scripts.
ores.sql.schema 7 Bi-temporal schema: table create/drop, insert triggers, notify triggers.
ores.sql.service 4 Service-registry SQL: service users, grants, accounts, roles.

See also

  • Parent: the ores physical-space root.

Emacs 29.3 (Org mode 9.6.15)