Urgent technical guidance- Drizzle/TiDB migration-ledger reconciliation

[jamiebrookes]

Hello Drizzle Team,

We are developing FireInspect, a commercial fire and life safety software platform, and have encountered a migration-ledger reconciliation problem that is blocking further database development.

Our environment:

• Drizzle Kit: 0.31.5
• Drizzle ORM: 0.44.6
• Database: TiDB
• Physical schema: 342 tables
• Migration ledger: 50 records, through migration 0049
• Migrations 0050–0082: 33 migrations whose schema effects appear to exist physically, but which are not recorded in the ledger

All 50 recorded SQL hashes match their migration files. Three ledger timestamps differ from the journal.

The pinned migration runner still attempts to execute all 33 migrations, potentially replaying existing DDL.

We have successfully restored a disposable database containing 342 tables and 17,031 rows, without changing its schema or ledger fingerprints.

We need authoritative guidance on:

1. The supported procedure for reconciling the migration ledger with an already-populated TiDB schema.
2. Whether Drizzle Kit 0.31.5 supports safe baseline adoption without replaying existing DDL.
3. How to address the three timestamp differences.
4. How to verify that the migration runner recognizes zero pending historical migrations.
5. Whether a version-specific migration fix or upgrade is required.

We will not modify production or manually alter migration hashes without a validated procedure.

Could a Drizzle maintainer provide or review a supported recovery approach that we can first test on a disposable database?

We can provide sanitized migration inventories, runner details and reproduction evidence.

Thank you.

[AndriiSherman]

Hey @jamiebrookes!
Yes, we can help you. You can email me, and we can set up a call so you can walk me through it
Please use: sherman@drizzle.team