jason/breedr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: Migration 003 - dynamic column restore to handle missing updated_at #42

Merged
jason merged 1 commits from fix/migration-003-dynamic-columns into master 2026-03-10 14:32:37 -05:00
Conversation 0 Commits 1 Files Changed 1 +41 -53
jason commented 2026-03-10 14:32:12 -05:00
Owner
Copy Link

Problem

Migration 003 hardcoded updated_at in the INSERT ... SELECT restore statement. The old health_records table never had an updated_at column (it was only added in newer schema versions via ALTER TABLE), so the migration crashed with:

no such column: updated_at

Fix

Instead of hardcoding the column list, Migration 003 now:

  1. Runs PRAGMA table_info(health_records_migration_backup) after creating the backup
  2. Builds the restore column list dynamically — only including columns that actually exist in the backup
  3. Logs both the detected columns and restored columns for transparency

New columns added in the fresh table (updated_at) will receive their DEFAULT (datetime('now')) value automatically for any restored rows.

Result

Migration 003 is now resilient to any column additions that happened via ALTER TABLE on old installs.

## Problem Migration 003 hardcoded `updated_at` in the `INSERT ... SELECT` restore statement. The old `health_records` table never had an `updated_at` column (it was only added in newer schema versions via `ALTER TABLE`), so the migration crashed with: ``` no such column: updated_at ``` ## Fix Instead of hardcoding the column list, Migration 003 now: 1. Runs `PRAGMA table_info(health_records_migration_backup)` after creating the backup 2. Builds the restore column list dynamically — only including columns that **actually exist** in the backup 3. Logs both the detected columns and restored columns for transparency New columns added in the fresh table (`updated_at`) will receive their `DEFAULT (datetime('now'))` value automatically for any restored rows. ## Result Migration 003 is now resilient to any column additions that happened via `ALTER TABLE` on old installs.
jason added 1 commit 2026-03-10 14:32:12 -05:00
fix: Migration 003 - use dynamic column list to handle missing updated_at in old schema e17ce2be29
jason merged commit d5bce0522b into master 2026-03-10 14:32:37 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jason/breedr#42
Delete Branch "fix/migration-003-dynamic-columns"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?