Every time I run drizzle-kit push --force when the previous __old_push table doesn't exist, with the next error:
LibsqlError: SQLITE_UNKNOWN: SQLite error: no such table: main.__old_push_parties
I've logged the statements that drizzle-kit executes for the migration, and apparently in performs DROP TABLE __old_push_table for the first command. I believe that the reason this migration fails because the previous statement lacks IF EXISTS.
Expected behavior
I'd expect it not to fail when I simply want to push my changes without caring about the old data.
Environment & setup
I'm running that on arch with node@20, but I have that script on a github runner with ubuntu-latest which uses oven-sh/setup-bun@v2 and it also fails with the same error.
What version of
drizzle-orm
are you using?0.33.0
What version of
drizzle-kit
are you using?0.24.0
Describe the Bug
Every time I run
drizzle-kit push --force
when the previous__old_push
table doesn't exist, with the next error:LibsqlError: SQLITE_UNKNOWN: SQLite error: no such table: main.__old_push_parties
I've logged the statements that
drizzle-kit
executes for the migration, and apparently in performsDROP TABLE __old_push_table
for the first command. I believe that the reason this migration fails because the previous statement lacksIF EXISTS
.Expected behavior
I'd expect it not to fail when I simply want to push my changes without caring about the old data.
Environment & setup
I'm running that on
arch
withnode@20
, but I have that script on a github runner withubuntu-latest
which usesoven-sh/setup-bun@v2
and it also fails with the same error.This is how my
drizzle.config.ts
looks like: