Table Status: Missing, Drift, Matched, Extra
The status makes the table-level comparison explicit.
Read articleTopic
database
Reading an ER Diagram for API Review
The diagram turns the reconciliation into a visual map.
Read articleRead-Only Database Access and Safety
The desktop reads the live schema, but it cannot write.
Read articleInferring Many-to-Many Link Tables
A join table is inferred from the shape, not forced into one side.
Read articleImpact of an API Change on the Database
The change is traced in both directions, not just one.
Read articleDeriving a Data Model from OpenAPI
The modeling layer closes the gap between the API and the database.
Read articleAn Additive Migration Plan and BlockedBy
The plan is ordered and additive, not a destructive rebuild.
Read articleAn agent ships the forward migration and forgets the way back
The forward migration applies cleanly, but the PR omits rollback, old-row backfill, and a read-after-write check. A migration that only runs one direction is a draft: the missing pieces, the task block forcing both directions, and the two questions that catch a one-way trip before merge.
Read article