Skip to content

fix(slm): add tablename collision check for dual SQLAlchemy bases (#1878)#2205

Open
mrveiss wants to merge 1 commit intoDev_new_guifrom
fix/issue-1878
Open

fix(slm): add tablename collision check for dual SQLAlchemy bases (#1878)#2205
mrveiss wants to merge 1 commit intoDev_new_guifrom
fix/issue-1878

Conversation

@mrveiss
Copy link
Owner

@mrveiss mrveiss commented Mar 23, 2026

Summary

Test plan

  • SLM starts without errors
  • Warning logged if intentionally shared tablenames exist
  • No false positives for legitimate separate-database tables

🤖 Generated with Claude Code

)

Add _check_tablename_collisions() startup check that detects shared
tablenames across both SQLAlchemy Base MetaData objects. Logs WARNING
for overlaps to catch misplacement bugs early (like #1854). Does not
raise since some names are intentionally shared across databases.
@github-actions
Copy link

✅ SSOT Configuration Compliance: Passing

🎉 No hardcoded values detected that have SSOT config equivalents!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant