Reason being, I'm building with (https://encore.dev) where the system needs to apply the migrations on startup, I managed to generate migrations with drizzle but each time I generate it does not track the state of the database schema, which makes sense. But if there was a way to mark a migration as applied, drizzle can still keep track of changes in the schema.
Please let me know if this makes sense or if I should approach this differently.
My workflow: - Create drizzle schema - Generate migrations with drizzle-kit - Start up encore that applies the migration based on the index of the migration file name - Change column name in schema Generate migration again but just drizzle-kit does not recognise previous migration as a new migration just contains
Encore is a Development Platform that lets you build robust distributed systems, using a high-performance backend framework with declarative infrastructure.