feat: multiple backup schedules per database #108

New Issue

MrUnknownDE · 2026-04-05T16:15:46+02:00

MrUnknownDE commented

2026-04-05 16:15:46 +02:00

Originally created by @commKnightWeb on 2/21/2026

Summary

Changed backup_configs primary key from database_id to id (UUID)
Added name field to identify distinct schedules for the same DB
Updated Backup core model to log which BackupConfigID created it
Refactored BackupConfigController to support creating, fetching lists, updating, and removing distinct configurations per database
Updated backend scheduler and cleaner components to map retentions and backup executions correctly utilizing discrete schedules

Test Plan

Run make lint / go test ./... in the backend
Verify multiple schedules insert and retrieve accurately through API tests
Tested clean backup database ID transfer loops internally

*Originally created by @commKnightWeb on 2/21/2026* ## Summary - Changed `backup_configs` primary key from `database_id` to `id` (UUID) - Added `name` field to identify distinct schedules for the same DB - Updated `Backup` core model to log which `BackupConfigID` created it - Refactored `BackupConfigController` to support creating, fetching lists, updating, and removing distinct configurations per database - Updated backend scheduler and cleaner components to map retentions and backup executions correctly utilizing discrete schedules ## Test Plan - [x] Run `make lint` / `go test ./...` in the backend - [x] Verify multiple schedules insert and retrieve accurately through API tests - [x] Tested clean backup database ID transfer loops internally

MrUnknownDE closed this issue

2026-04-05 16:15:46 +02:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/databasus#108