Version Specific Sql Map Selection

When monitoring or querying many RDBMS products across many versions (Oracle 9i–23c, MySQL 5.7–9.6, MariaDB 10.6–12.2, PostgreSQL 9.6–18, MSSQL 2012–2022, Tibero 4–6, CUBRID 9.1–11.3), maintain one SQL map XML per (DBMS, majorVersion) tuple and resolve the correct map at runtime.

Shape

• File naming: sql_map_<DBMS>_<VERSION>.xml in a single resources folder.
• Registry: boot-time scan loads every matching file into Map<(dbms,version), Map<queryId, sql>>.
• Lookup: getQuery(dbms, rawVersion, queryId) runs rawVersion through a per-DBMS version normalizer, then falls back to a known-good default when the normalizer rejects it.
• Fallback rationale: unknown target version is better served by the closest supported version than a hard failure — collection keeps running.

Steps

1. Define a DbmsVersionResolver interface: String resolve(String rawVersion); one impl per DBMS.
2. In each impl, map raw version strings to the nearest supported bucket (e.g. 10.x, 11.x, 12.x → ; unknown → documented default).