Guides
Loading documentation…
Preparing this guide.
Loading page content
Link a Drizzle or Prisma project, see how its schema has drifted from the live database, and preview a migration before you run it.
The ORM Cockpit connects your code to your running database. Link a project folder, and Dora reads its Drizzle or Prisma schema, compares it against the live database, and shows you exactly where the two have drifted apart. When there is drift, Dora generates a dialect-correct migration you can review before anything touches the database.
drizzle.config.* / schema files) or Prisma schema (prisma/schema.prisma)
and parses it into an internal schema model.Drift is grouped per table so you can scan it quickly. Each change is classified by how risky it is to apply:
| Classification | Meaning | Examples |
|---|---|---|
| Safe | Additive, non-destructive | Add a new table, add a nullable column |
| Review | Could affect existing data | Change a column type, add a constraint |
| Destructive | Removes or rewrites data | Drop a column, drop a table |
This lets you see at a glance whether a migration is a routine additive change or something that needs care.
When you open the migration preview, Dora shows the generated SQL statements in order. Safe statements are ready to go. Review and destructive statements are gated behind an explicit opt-in: you have to consciously include them before they become part of the SQL handed to the query console.
From there you run the SQL in Dora's console like any other query, with the generated statements in front of you the whole time. Nothing is applied silently.
drizzle.config.*prisma/schema.prismaIf you write type-safe queries with these ORMs, see the ORM Runners guide for running Drizzle and Prisma Client queries directly inside Dora.