[Yaraslaut]

Summary

dbtool.yml can now name where backups go, so a deployment (for example an installer) can pre-configure it and dbtool and dbtool-gui both honor it.

defaultBackupDir: D:/backups          # store-wide fallback
profiles:
  prod:
    backupDir: D:/backups/prod        # optional per-profile override

Closes #658

Resolution

Mirrors pluginsDir: the profile's backupDir, then the top-level defaultBackupDir, then the previous behaviour.

• dbtool backup: a bare file name in --output, or no --output at all (it then writes <profile>-<YYYYMMDD-HHMMSS>.zip, local time), goes into that folder, which is created if missing. A path with a directory part is used exactly as given. The file that was written is printed. With no folder configured --output is required, as before.
• dbtool add-profile --backup-dir <DIR>, and list-profiles shows an effective BACKUPDIR column.
• dbtool-gui: defaultBackupDir becomes the default backup folder, unless a folder was chosen in Settings (which still wins). Settings' placeholder and help show the folder that will really be used.
• Docs: docs/dbtool.md and the GUI README.

Decisions worth a look

• GUI and per-profile backupDir. The Backups page keeps every profile's archive in one folder (one folder card, one folder check, <profile>.zip inside it), so only the store-wide defaultBackupDir applies there; a per-profile backupDir is a CLI feature. Honoring it in the GUI would mean a per-profile folder model, which felt out of scope. The issue's "use the resolved folder" is ambiguous on this, so I took the reading that does not change the page's model. Say if you want the other one.
• --connection-string without --profile applies no profile, and therefore no backup folder, like every other profile default. --output stays required there.
• Relative paths are used as written (relative to the working directory), like pluginsDir.
• Bug found on the way. ProfileFileEditor listed the fields of a new profile in two places: the text it renders, and the document it verifies its own edit against. Adding a field to only one made every add-profile that carried it fail with "could not be edited exactly". Both now come from one table, so they cannot drift apart again.

Performance impact

None: configuration parsing and a path decision.

Risk assessment

• Per DBMS: none, no database code changed.
• Behaviour change: only for files that contain the new keys. Without them dbtool backup behaves exactly as before. Profile and NewProfile gained a defaulted field at the end, so existing aggregate initialisations are unaffected.
• Generated name: uses local time and replaces characters that are unsafe in a file name with _.
• Overlap with dbtool-gui: Backup & restore panel, Settings in Simple mode, add profiles #662. That PR also changes dbtool/main.cpp's add-profile (it moves it onto a shared AddProfileToFile) and ProfileFileEditorTests.cpp. Whichever merges second needs a small rebase: ProfileRequest there will need a backupDir field and the --backup-dir wiring moved onto it. I kept this PR on master so it does not depend on dbtool-gui: Backup & restore panel, Settings in Simple mode, add profiles #662.

Testing

• Suites run locally (Windows clang-cl, release, SQLite): the new [backup-dir] tests, [ProfileStore], [ProfileFileEditor], [profile-add], test_dbtool.py --test-env sqlite3 (which now covers add-profile --backup-dir, list-profiles, bare name, generated name, explicit path, defaultBackupDir fallback and the unchanged error without a folder), and the dbtool-gui Catch2 and QML suites.
• Linux, Qt 6.8.0, clang 19: dbtool, dbtool-gui and the GUI test targets (Catch2, QML, smoke) build and pass.
• Not run: GCC (the WSL GCC tree cannot configure here, no OpenSSL dev headers), clang-tidy, MSSQL and PostgreSQL, the C++26 reflection and modules builds. No database code changed.
• Known local failures unrelated to this change: two existing GUI tests assume no profile is loaded but the developer's real %APPDATA%\dbtool\dbtool.yml is auto-discovered. They pass on CI and on Linux.
• /simplify was not run.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!