Skip to content

Models

To persist a new kind of record, follow an existing UUIDBase model. Define who owns the row, who may read or change it, and how it survives or expires. The permission check belongs to the operation that accesses it.

  1. Add the mapping to Core's database models and import it in the explicit model catalogue. The Alembic environment imports this catalogue to obtain the metadata.
  2. Supply the corresponding migration. Exercise the revision against PostgreSQL. The Blockworld migration cases compare the migrated columns with the ORM models, cycle an empty schema, and check that downgrade refuses retained records. Choose cases that cover your revision's data and recovery contract. The revision-generation test checks the formatting hooks on a new revision file.

The current extension context has no model store. Schema evolution follows the Core migration path and the provenance and recovery obligations of Persistence.