django__django-11630

Django throws error when different apps with different models have the same name table name.

Verdict: the fix is stated in the issue (Tier A).

My opinion is that as soon as the project has a non-empty DATABASE_ROUTERS setting, the error should be turned into a warning

The text states the fix: “My opinion is that as soon as the project has a non-empty DATABASE_ROUTERS setting, the error should be turned into a warning”

All SWE-bench Lite tasks · more django/django tasks · How the check works