officerdev/platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

drop the unapplied migration history

Browse Source 
The seven files in officer_db/migrations/ were never applied — this database has
only ever been managed with db:push, so there is no __drizzle_migrations table
and the numbered history had drifted from the real schema (0001 creates a
saved_sessions table the database does not have).

Deleted so there is one story about how the schema gets applied. db:gen can
write a fresh baseline from the current schema.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
brunorezio
2026-07-25 23:30:20 +01:00
co-authored by Claude Opus 5
parent 0e71d87f75
commit 10400310c5
16 changed files with 7 additions and 15233 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+7 -3
View File
@@ -83,9 +83,13 @@ where terminals, chats and task runs actually execute).
### Schema changes use `push`, not migrations
This database is kept in sync with `bun db:push`. **`drizzle-kit migrate` has never been run here**
— there is no `__drizzle_migrations` table, and the files in `officer_db/migrations/` are historical
residue that does not describe the live database. Change the schema, run `bun db:push`, done.
This database is kept in sync with `bun db:push`, which diffs the schema code against the live
database and alters it directly. **`drizzle-kit migrate` has never been run here** — there is no
`__drizzle_migrations` table. Change the schema, run `bun db:push`, done.
`bun db:gen` writes files to `officer_db/migrations/`, but nothing applies them; the old numbered
history was deleted because it had drifted from the real schema. Treat the schema code, not those
files, as the source of truth.
## Security Model