Skip to main content

Rename Exemption for ORM-Generated Models and Migration Freeze

Context

If drogon_ctl-generated model classes undergo manual renaming, regeneration drifts immediately; if already-applied migrations are modified, multi-environment schema validation breaks.

Decision

The 14 drogon_ctl-generated model class names/namespaces are never renamed (this overrides the unified naming style; only whole-directory relocation is allowed); merged V### migration files are frozen, and schema changes only append new versions.

Consequences and Current State

This decision was validated through both the repo refactor and the SDK refactor; migration-check (M5) enforces migration immutability in CI; keeping the oauth2_* table/class names intact during the 2026-08 renaming project is precisely this ADR in action.