weird __drizzle_migrations row id (move from `drizzle-kit push` to `drizzle-kit migrate`)
tl;dr: how is the starting id defined when running
i had to forego the described challenge in the title. seemed trivial, but i found a few pitfalls in the dx.
i tried to manually create the rows in the drizzle table but the it's unclear how the index is defined. i had 10 migrations: locally, the id started in
i worked my way around it by setting
drizzle-kit migrate? i though it was the migration filename id but it doesn't seem to be.i had to forego the described challenge in the title. seemed trivial, but i found a few pitfalls in the dx.
i tried to manually create the rows in the drizzle table but the it's unclear how the index is defined. i had 10 migrations: locally, the id started in
25. in my remote db, it started in 4.i worked my way around it by setting
SELECT 1; temporarily in my migration files so the drizzle-kit migrate command would fill the __drizzle_migrations table; although the hash doesn't match the contents it doesn't matter because the command uses the index.