MySQL 26.x (calendar versioning) rejected: "unsupported MySQL major version: 26"

Databasus version (screenshot)

v3.57.0 (screenshot attached in a comment below)

Operating system and architecture

Ubuntu 24.04 ARM64 (Oracle Cloud VM.Standard.A1.Flex), Databasus running in Docker

Database type and version (optional, for DB-related bugs)

MySQL 26.7.0 on Oracle Cloud (MySQL HeatWave DB System). SELECT VERSION() returns 26.7.0-cloud.

Describe the bug (please write manually, do not ask AI to summarize)

What happened:

Adding a MySQL HeatWave database and clicking "Test connection" fails with:

unsupported MySQL major version: 26 (supported: 5.x, 8.x, 9.x)

MySQL switched to calendar-based versioning after 9.7: the first release under the new scheme is 26.7.0 (GA 2026-07-28, https://dev.mysql.com/doc/relnotes/mysql/26.7/en/). It is the direct continuation of the 9.x line, so the bundled 9.x mysqldump client should work with it, but mapMysqlVersion in backend/internal/features/databases/databases/mysql/model.go only accepts major 5, 8 and 9 and rejects everything else.

Oracle's managed MySQL (HeatWave) already ships 26.7.0, so anyone backing up a HeatWave instance is blocked. Community MySQL will follow as 26.x rolls out.

What I expected:

The connection test passes and 26.x is handled like 9.x.

Steps to reproduce

1. Run any MySQL 26.7.0 instance (e.g. an Oracle Cloud MySQL HeatWave DB System, or the mysql:26.7 image once available).
2. In Databasus, add a MySQL database pointing at it.
3. Click "Test connection".

Have you asked AI how to solve the issue?

• Claude Sonnet 4.6 or newer
• ChatGPT 5.2 or newer
• No

Additional context / logs

Suggested fix in mapMysqlVersion: treat any major >= 9 as tools.MysqlVersion9 instead of listing majors explicitly, so future calendar versions (27.x, ...) do not need a new case each time. Happy to open a PR if that approach is acceptable.