[Bug] Postgres migrations are broken on 0.23.10
Re-running the same postgres migration twice just throws an error that a particular table already exists. It looks like its always trying to deploy the first migration instead of using drizzle migrations table to reference and compare hashes
13 Replies
@bloberenober @Andrii Sherman can you let me know if this is a regression - not sure whats going on...
@rushil1o1 would be great if you can share a content of
meta._journal,json
and drizzle.__drizzle_migrations
table
There shouldn't be any sensitive info, but will help a bit to find a causeFor sure
thanks!
FYI: its easily reproducible for us -- re-running the migration command twice will throw an error instead of just succeeding
Could you enable the query logging by passing
{logger: true}
to the drizzle()
call and post the queries that the migrator runs? (you can filter out your actual migrations from the logs, I'm just interested in the queries added by the migrator)``````
one last question I guess
what driver do you use for migration? pg or postgres.js?
also did this issue appear after some update? or you never run migrations previously
drizzle-orm/node-postgres/migrator
happened from 0.23.8 -> 0.23.9/10
ok, great
thanks for all the info. Checking it now
@rushil1o1 just found
going to release fix and add tests for that asap
[email protected]
please try this outPerfect will try soon
yup - all good, works @Andrii Sherman - thank you!
Thank you also. It was a critical one for everyone using Postgres
You helped us to find a problem faster