sneak/vaultik
1
0
Fork 0
Code Issues 20 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

No database migration support — schema changes require full re-backup #17

New Issue
Open
opened 2026-02-08 17:16:53 +01:00 by clawbot · 0 comments
clawbot commented 2026-02-08 17:16:53 +01:00
Collaborator
Copy Link

The schema file explicitly states:

Note: This database does not support migrations. If the schema changes, delete the local database and perform a full backup to recreate it.

For a 1.0 release, this is a significant limitation. Any schema change post-1.0 would require users to delete their local DB and do a full re-backup, which could be very slow. Should implement at minimum a schema version check and basic migration support.

Ref: parent issue #1

The schema file explicitly states: > Note: This database does not support migrations. If the schema changes, delete the local database and perform a full backup to recreate it. For a 1.0 release, this is a significant limitation. Any schema change post-1.0 would require users to delete their local DB and do a full re-backup, which could be very slow. Should implement at minimum a schema version check and basic migration support. Ref: parent issue #1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sneak/vaultik#17
No description provided.
Delete Branch "%!s()"

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?