data-model-design

To design a data model effectively, this Skill guides you in planning entities, relationships, and cross-module references while maintaining module boundaries. It enforces standard conventions like UUID v4 primary keys for robust database schemas.

The best way to handle database migrations for tenant-scoped modules is using standard migration tooling like yarn db:generate and yarn db:migrate. This provides consistency guarantees and guides the migration lifecycle from scaffolding to deployment.

To plan a new data model with an ORM, you define your entities and relationships using standard templates. This process guides relationship patterns and enforces primary key conventions before applying database migrations.

Yes, this data model design approach works with Postgres by enforcing standard columns and UUID v4 primary keys. It supports the migration lifecycle using yarn db:generate and yarn db:migrate commands tailored for Postgres databases.

When designing entities, standard columns and UUID v4 primary keys are required to follow Open Mercato conventions. These standard templates ensure consistency across entities and maintain robust relationship patterns.

You should run yarn db:migrate after you generate migrations with yarn db:generate and define your entities. This sequence applies the scaffolded migrations to your database, ensuring consistency and proper dependency mapping.