powerhousejnr248
DTDrizzle Team
•Created by powerhousejnr248 on 9/11/2024 in #help
Marking Migrations
Oh ok thanks @Angelelz , this was because I used no prefix and manipulated the file name, but I'll find a work around
10 replies
DTDrizzle Team
•Created by powerhousejnr248 on 9/11/2024 in #help
Marking Migrations
Hey @Angelelz , thanks for the response. To clarify further, the reason Drizzle isn't recognizing the changes is that Encore is applying the migrations using its own migration strategy. I’m just using Drizzle to generate the migrations with
drizzle-kit.
What I want is to mark a migration as applied (similar to Django's --fake option) so Drizzle recognizes the latest migration without actually applying it to the database schema. This way, Drizzle won’t generate redundant CREATE TABLE statements, but will still track the state of the schema and the applied migrations correctly.
Does that help clarify my situation? I'd appreciate any suggestions on how to approach this10 replies
DTDrizzle Team
•Created by powerhousejnr248 on 9/11/2024 in #help
Marking Migrations
Yes it saves index, hash and date created, can I apply this migration marking without applying the migration to my database schema ?
10 replies