为何Django inspectdb无法为现有数据库正确生成外键？

I totally get this frustration—inspectdb is a huge time-saver, but it often drops the ball when it comes to detecting foreign key relationships, especially if your existing database doesn’t have explicit foreign key constraints set up. Let’s walk through how to fix this properly.

Why This Happens #

Django’s inspectdb tool relies on database-level foreign key constraints to automatically generate ForeignKey fields. If your database tables don’t have those constraints defined (even if you logically know the relationship exists), it’ll default to creating an IntegerField instead, since that’s the underlying data type for most foreign key columns.

Step-by-Step Fix #

Let’s use your example to break this down:

Original generated code:

user_id = models.IntegerField(blank=True, null=True)

Correcting the Field

You’ll want to replace that IntegerField with a ForeignKey, but there are a few details to get right:

user = models.ForeignKey(
    'User',
    on_delete=models.CASCADE,
    blank=True,
    null=True,
    db_column='user_id'  # Critical: tells Django to use the existing 'user_id' column
)

• Field Name: I renamed it from user_id to user because that’s Django’s convention (the ORM will handle mapping to the user_id column via db_column). If you prefer keeping user_id as the field name, you can do that too—just make sure db_column matches your actual database column name to avoid errors.
• on_delete: This is required in Django. Choose the option that fits your business logic (e.g., CASCADE to delete related objects when the User is deleted, PROTECT to prevent deletion if related objects exist, SET_NULL to set the field to null if allowed).
• blank/null: Keep these matching the original field since your database allows null/blank values.

Bulk Fix Tip

If you have dozens of these fields to update, use your code editor’s find-and-replace with regex to speed things up. For example:

• Find: (\w+)_id = models.IntegerField\(blank=True, null=True\)
• Replace: \1 = models.ForeignKey('\u\1', on_delete=models.CASCADE, blank=True, null=True, db_column='\1_id')
  Note: This assumes your model names are the singular, capitalized version of the field prefix (e.g., user_id → User). You’ll need to tweak it for any exceptions (like post_id → Post).

Preventing This in the Future #

If you have control over the database schema, add explicit foreign key constraints to your tables. Next time you run python manage.py inspectdb, Django will automatically generate the correct ForeignKey fields instead of IntegerFields.

内容的提问来源于stack exchange，提问作者Abdul Haseeb