2 people reported
All time, since Apr 22.
libsql migrations table uses SERIAL
“After creating the __drizzle_migrations table, the ID is NULL on running migrations.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/drizzle/issues/5170/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
libsql migrator creates migrations table with Postgres SERIAL id. The __drizzle_migrations table uses SERIAL instead of INTEGER PRIMARY KEY AUTOINCREMENT; migrate hangs or the ID is NULL.
Is this your bug?
File my report- Where
- libsql migrator
- Versions
- 0.45.2
- How bad
- Breaks a normal workflow.