harddjango/django · v3.0

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

web ormbase 65e86948b8

Mode

60 minutes, the full token budget.

Time limit60 min
Token budgetup to 1M
Worth up to310 XP

Opens VS Code with an AI agent in a new tab. Prompts, tokens, tool calls and test runs are recorded and scored.

Problem statement

Description

Error message:
table_name: (models.E028) db_table 'table_name' is used by multiple models: base.ModelName, app2.ModelName.
We have a Base app that points to a central database and that has its own tables. We then have multiple Apps that talk to their own databases. Some share the same table names.
We have used this setup for a while, but after upgrading to Django 2.2 we're getting an error saying we're not allowed 2 apps, with 2 different models to have the same table names.
Is this correct behavior? We've had to roll back to Django 2.0 for now.

The environment starts at commit 65e86948b802 (django/django 3.0), dependencies installed and tests runnable from the first minute. You are graded by hidden tests taken from the fix that was actually merged upstream.