Replies: 1 comment
-
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 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 |
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions