How to mark a migration as applied?

[mbrevda]

When adopting drizzle to an existing project, the workflow seems to be:

1. run introspect:pg to generate the schema
2. run the generated migration so that it's marked as applied in the db

Often the migration cannot be re-run as it contains commands that cannot be reapplied (e.g. re-creating a primary key).

So how can this migration be marked as applied?

[capaj]

this is very easy in prisma as they rely on the migration name as primary key for identifying the migration. Too bad in drizzle there is a hash and no easy way to calculate the hash from the CLI

[jwatte]

That is not a particularly helpful comment, because we're using drizzle, not prisma.
I think using the hash is safer because otherwise who knows what version of the file named 0099_upgrade_stuff.sql was actually applied?
But, we need to mark a particular migration as applied when it requires manual fix-up; for example, when altering primary keys in postgres, which drizzle migrations fail to do correctly.