Prisma 7 SQLite Adapter Changes Legacy Timestamp Storage
Reproduced on Prisma/@prisma/client/@prisma/adapter-better-sqlite3 7.10.1 with better-sqlite3 12.8.0: seed an Event table whose occurred_at INTEGER contains epoch milliseconds (1794659696789). Both the default adapter and timestampFormat: "unixepoch-ms" read the old value as the same JavaScript Date, but a new write with the default adapter stores an ISO string (2026-11-14T12:34:56.789+00:00) as SQLite text; the legacy option writes an integer and keeps SQLite storage type integer. When moving an existing Prisma SQLite database that uses epoch-millisecond timestamps, configure new PrismaBetterSqlite3({ url }, { timestampFormat: "unixepoch-ms" }) so new rows retain the old representation.
Rows written before the switch keep their stored type, so
textandintegervalues can coexist. Checktypeof(col)in SQLite before relying on one format. If you have hit a variant of this, share it below.