DB name field is not optional #341

New Issue

MrUnknownDE · 2026-04-05T16:16:14+02:00

MrUnknownDE commented

2026-04-05 16:16:14 +02:00

Originally created by @mlongo4290 on 12/19/2025

I'm using v2.8.0.
DB Name field is de-facto mandatory.
When configuring a new backup job, the "DB name" field is labeled as optional (according to the placeholder), but leaving it empty keeps the "Test connection" button disabled. This makes the field de-facto mandatory and prevents the setup of instance-level backups.
I am currently managing about 100 databases on a single host. Configuring a separate job for each database is not scalable. It would be a significant improvement to allow the creation of a single backup job that covers all databases on a host (using a wildcard or a "Select All" option) instead of requiring one job per database.

*Originally created by @mlongo4290 on 12/19/2025* I'm using v2.8.0. DB Name field is de-facto mandatory. When configuring a new backup job, the "DB name" field is labeled as optional (according to the placeholder), but leaving it empty keeps the "Test connection" button disabled. This makes the field de-facto mandatory and prevents the setup of instance-level backups. I am currently managing about 100 databases on a single host. Configuring a separate job for each database is not scalable. It would be a significant improvement to allow the creation of a single backup job that covers all databases on a host (using a wildcard or a "Select All" option) instead of requiring one job per database. <img width="421" height="427" alt="Image" src="https://github.com/user-attachments/assets/b718b979-b4cd-43c4-978e-ca2ecddb1f56" />

MrUnknownDE closed this issue

2026-04-05 16:16:14 +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#341