__drizzle_migrations table

[DNoel26]

I'm new to drizzle and was just wondering what this table is used for? I'm in the process of running my first few test migrations and noticed a record being created with id, hash and created_at with each migration run.

[adpadillar]

I know this is late, but I recently was doing some research on it myself and it basically tracks which migrations you have run and when. For example, imagine a developer has a dev database that has ran migrations 1, 2, 3 and some other dev created migrations 4 and 5 later. After the first dev merges the other dev's changes to his own, he can run drizzle-kit migrate and this will basically check the migrations table and notice it only has to run migrations 4 and 5, so it will go ahead and do that

Note: I have not experimented with this enough to see if it can handle more complex situations, like simultaneous (but not conflicting) schema changes. Imagine if dev 1 where to add migrations A and B while dev 2 added migrations C and D, then as long as they don't conflict the ideal behavior would be for dev 1 to execute migrations C and D only, while dev 2 executes A and B. If I ever do confirm this is the case, I will come back and report

[pppdns]

I'm wondering why Drizzle is not simply storing the migration file name instead of this hash. It would be infinitely more useful for seeing which migrations were run and which ones weren't. This is how most other ORM-s track migrations in the database. Drizzle migrations are very difficult to fix or debug when they go wrong, as you don't see which migrations ran successfully