fix(sqlalchemy-spanner): isolate test database names and extend stale cleanup cutoff - #18160

Draft

chalmerlowe wants to merge 11 commits into

mainfrom

fix/sqlalchemy-spanner-db-isolation

Commits on Aug 19, 2026

fix(sqlalchemy-spanner): isolate test database names and extend stale cleanup cutoff
chalmerlowe
committed
89c2455
fix(sqlalchemy-spanner): retain full 10-digit timestamp in db name and validate metadata dict type
chalmerlowe
committed
ec9200f
fix(sqlalchemy-spanner): protect active test database from accidental garbage collection
chalmerlowe
committed
fa9ca91
fix(sqlalchemy-spanner): remove test.cfg lookup in cleanup and use generous 1-hour cutoff
chalmerlowe
committed
774d4f4
fix(sqlalchemy-spanner): align database cleanup cutoff with 4-hour instance threshold
chalmerlowe
committed
1bad94e
fix(sqlalchemy-spanner): eliminate startup stale database cleanup to prevent cross-session drops
chalmerlowe
committed
c95ec89
fix(sqlalchemy-spanner): add sentinel-guarded 4-hour stale database cleanup
chalmerlowe
committed
0ff6754
fix(sqlalchemy-spanner): isolate test config per nox session to prevent cross-session database drops
chalmerlowe
committed
8057ab5
fix(sqlalchemy-spanner): explicitly pass --dburi to pytest to prevent fallback to sqlite
chalmerlowe
committed
a7cfa9c
fix(sqlalchemy-spanner): define config_file in system session scope to avoid NameError
chalmerlowe
committed
d7df95e
fix(sqlalchemy-spanner): use Spanner-compliant database ID format with underscores instead of hyphens
chalmerlowe
committed
b2fbe29