Comprehensive Guide to Django MySQL Configuration: From Development to Deployment

Understanding Django Development Server Operation Modes

In Django development, using the python manage.py runserver command to start the development server is standard practice. When you execute python manage.py runserver myip:port, this actually allows other machines to access your development application. In development environments, simply running python manage.py runserver (without IP and port parameters) is usually sufficient as it only permits local access. Understanding this distinction is crucial for differentiating between development and production environments.

MySQL Database Connection Configuration

To configure Django to use MySQL database, you need to modify the DATABASES dictionary in your project's settings.py file. The basic configuration example is as follows:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'DB_NAME',
        'USER': 'DB_USER',
        'PASSWORD': 'DB_PASSWORD',
        'HOST': 'localhost',
        'PORT': '3306',
    }
}

In this configuration:

• ENGINE specifies using MySQL backend
• NAME is the database name
• USER and PASSWORD are database credentials
• HOST set to localhost indicates local database server
• PORT defaults to MySQL's standard port 3306

Advanced Configuration Using MySQL Option Files

Starting from Django 1.7, support for MySQL option files for connection configuration was introduced. This method offers better security and flexibility:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'OPTIONS': {
            'read_default_file': '/path/to/my.cnf',
        },
    }
}

The corresponding MySQL configuration file content should be:

[client]
database = DB_NAME
host = localhost
user = DB_USER
password = DB_PASSWORD
default-character-set = utf8

The configuration priority rule is: settings in OPTIONS take precedence over direct parameters like NAME, USER, etc., and direct parameters override settings in MySQL option files.

Character Encoding and Database Creation

MySQL's default character set is often not UTF-8, which can lead to Unicode character handling issues. To ensure proper character support, create the database using:

CREATE DATABASE mydatabase CHARACTER SET utf8 COLLATE utf8_bin

This ensures all tables and columns use UTF-8 encoding by default, preventing potential data truncation or encoding errors.

Python MySQL Driver Selection

Django supports multiple MySQL Python drivers:

• mysqlclient: Native driver, recommended choice, install with: pip3 install mysqlclient
• MySQL Connector/Python: Pure Python driver provided by Oracle, requires setting ENGINE to mysql.connector.django

Connection Management and Performance Optimization

Django's database connection management mechanism is crucial for application performance. The CONN_MAX_AGE parameter controls persistent connection lifetime:

• Default value is 0, closing connection at the end of each request
• Set to positive integer (seconds) to enable persistent connections
• Set to None for unlimited persistent connections

In development environments, since the development server creates a new thread for each request, the effect of persistent connections is negated, so they are not recommended during development.

Deployment Considerations

When preparing to deploy Django applications to production environments, consider these key factors:

• Use appropriate WSGI servers (like Gunicorn or uWSGI) instead of development server
• Configure proper database connection pooling settings
• Set correct environment variables to manage sensitive information
• Consider using MySQL's sql_mode settings to enhance data integrity

By following these configuration guidelines and best practices, you can ensure that Django's integration with MySQL is both stable and efficient, providing reliable data storage solutions for web applications.