Skip to content

docs: Add database backup guidance before schema migrations #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
evansenter merged 1 commit into from
Jan 2, 2026
Merged

docs: Add database backup guidance before schema migrations #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,13 @@ Key components:
- `make uninstall` - OK, preserves database (only removes LaunchAgent + MCP config)
- `make reinstall` - OK, just reinstalls Python package

### Before schema/migration changes:
**ALWAYS back up the database before making schema or migration changes:**
```bash
cp ~/.claude/contrib/analytics/data.db ~/.claude/contrib/analytics/data.db.backup-$(date +%Y%m%d-%H%M%S)
```
Migrations can have subtle bugs (race conditions, incorrect data transforms) that corrupt data irreversibly.

### If you need to test destructive operations:
Use a temporary database in tests (all tests already do this via `tmpdir`).

Expand Down