如何在Django中复用已有带SQL迁移的MySQL数据库？无需编写Django模型及生成迁移时需做哪些配置修改？

Hey there! I’ve helped a handful of developers set this up before, so let’s break down exactly what you need to do to use your pre-existing MySQL database in Django—no model files or migration headaches required. Here’s your step-by-step guide:

1. Install the MySQL Database Driver #

First, you need to let Django communicate with MySQL. Grab the right driver for your setup:

• For most environments, use mysqlclient (Django’s official recommended driver):

  pip install mysqlclient
  

• If you hit compatibility issues (common on some Windows/macOS setups), use pymysql as an alternative:

  pip install pymysql
  

  Then add these lines to your project’s root __init__.py to make Django treat it as the standard MySQL driver:

  import pymysql
  pymysql.install_as_MySQLdb()
  

2. Configure Django to Connect to Your Database #

Open your project’s settings.py file and replace the default DATABASES config with your MySQL details:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'your_existing_db_name',  # Name of your pre-existing MySQL database
        'USER': 'db_username',             # MySQL user with access to the database
        'PASSWORD': 'db_password',         # Password for the database user
        'HOST': 'localhost',               # Use your remote host if the DB isn't local
        'PORT': '3306',                    # Default MySQL port (adjust if needed)
        'OPTIONS': {
            'charset': 'utf8mb4',          # Optional but recommended for full Unicode support
        },
    }
}

3. Disable Django’s Migration System #

Since you don’t want to generate or apply any migrations (you’re using a fully built database), tell Django to skip migration handling entirely. You have two solid options:

Option A: Disable Migrations Globally #

Add this to your settings.py to prevent Django from looking for or running migration files:

MIGRATION_MODULES = {
    'django.contrib.auth': None,
    'django.contrib.contenttypes': None,
    'django.contrib.sessions': None,
    'django.contrib.messages': None,
    # Add any of your custom apps here (if you have them) and set their value to None
}

Option B: Skip Migrations Per Command #

If you prefer not to modify settings.py permanently, add the --no-migrations flag whenever you run Django commands:

python manage.py runserver --no-migrations
python manage.py shell --no-migrations

4. Query Your Existing Database Directly #

Now you’re ready to pull data from your tables! Since you’re skipping models, use Django’s built-in database cursor to execute raw SQL queries:

from django.db import connection

def fetch_existing_data():
    # Use a context manager to handle the cursor automatically
    with connection.cursor() as cursor:
        # Replace with your actual SQL query
        cursor.execute("SELECT id, name, created_at FROM your_existing_table LIMIT 10")
        # Fetch all results as a list of tuples
        results = cursor.fetchall()
        
        # Optional: Convert tuples to dictionaries for easier handling
        columns = [col[0] for col in cursor.description]
        results_as_dicts = [dict(zip(columns, row)) for row in results]
        
        return results_as_dicts

Quick Tips: #

• Ensure your MySQL user has at least SELECT permissions on the tables you need to access (add write permissions if you need to modify data).
• Never run python manage.py makemigrations or python manage.py migrate—these will attempt to alter your existing database structure, which you don’t want.
• For write operations, use cursor.execute() with INSERT/UPDATE/DELETE statements just like you would for SELECT queries.

内容的提问来源于stack exchange，提问作者nikhil khadse