Applying Migrations Fails with Error: Typ »account_enum« already exists

[riculum]

I am encountering an issue while running migrations for my PostgreSQL database using Drizzle Kit and Node.js. Recently, I had to restore my development database from a backup, but now I cannot apply any new migrations. The migration process fails with the following error:
error: Typ »account_enum« already exists

What I Understand So Far:
The error message (Typ »account_enum« already exists) suggests that an enum type account_enum already exists in the database schema. The migration process is likely trying to create it again, leading to a conflict.

My Question:
How can I handle this situation where:

• A migration attempts to create an enum (or other objects) that already exist after a database restore?
  

• New migrations cannot be applied due to conflicts between the restored database schema and the migration system?
  

Is there a way to:

• Mark existing migrations as applied?
  

• Reconcile the database schema with the migration history in Drizzle ORM?
  

[outranker]

Did you figure out a solution? I am trying to do basically the same thing. It would be great if we could mark the migration as applied

[kanian]

1. Find the migration that is the issue.
2. Right before the type that is giving you trouble:

DROP TYPE IF EXISTS "enum_name";

That should do it.