Database configuration in Django - Step-by-Step Execution

Concept Flow - Database configuration

Start Django Project

↓

Open settings.py

↓

Locate DATABASES dict

↓

Set ENGINE, NAME, USER, PASSWORD, HOST, PORT

↓

Save settings.py

↓

Run migrations

↓

Database ready for use

This flow shows how Django reads and applies database settings from settings.py to connect and prepare the database.

Execution Sample

Django

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': BASE_DIR / 'db.sqlite3',
    }
}

Defines a simple SQLite database configuration for Django project.

Execution Table

Step	Action	Setting Key	Value Set	Effect
1	Open settings.py	-	-	Ready to edit database config
2	Locate DATABASES dict	DATABASES	dict found	Database config section identified
3	Set ENGINE	ENGINE	django.db.backends.sqlite3	Use SQLite engine
4	Set NAME	NAME	BASE_DIR / 'db.sqlite3'	Database file path set
5	Save settings.py	-	-	Settings saved
6	Run migrations	-	-	Database tables created
7	Connect to database	-	-	Django ready to use database

💡 All required database settings configured and migrations applied, database ready.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
DATABASES	{}	{'default': {'ENGINE': 'django.db.backends.sqlite3'}}	{'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': BASE_DIR / 'db.sqlite3'}}	{'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': BASE_DIR / 'db.sqlite3'}}

Key Moments - 3 Insights

Why do we set 'ENGINE' in DATABASES?

The 'ENGINE' tells Django which database type to use, like SQLite or PostgreSQL. Without it, Django won't know how to connect. See execution_table step 3.

What happens if 'NAME' is incorrect?

'NAME' specifies the database location or name. If wrong, Django can't find or create the database file, causing errors. See execution_table step 4.

Why run migrations after configuring DATABASES?

Migrations create the necessary tables in the database based on your models. Without running them, the database is empty. See execution_table step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what value is set for 'ENGINE' at step 3?

A BASE_DIR / 'db.sqlite3'

B default

C django.db.backends.sqlite3

D postgresql

💡 Hint

Check the 'Value Set' column at step 3 in execution_table.

At which step does Django create the database tables?

A Step 4

B Step 6

C Step 2

D Step 7

💡 Hint

Look for the action 'Run migrations' in execution_table.

If you change 'ENGINE' to 'django.db.backends.postgresql', what else must you add?

A USER, PASSWORD, HOST, PORT settings

B Nothing else needed

C Only NAME setting

D BASE_DIR path

💡 Hint

PostgreSQL needs connection details beyond just ENGINE and NAME.

Concept Snapshot

Django database config lives in settings.py under DATABASES dict.
Set 'ENGINE' to choose database type (e.g., sqlite3, postgresql).
Set 'NAME' to database name or path.
For some DBs, add USER, PASSWORD, HOST, PORT.
Run 'migrate' to create tables.
Django uses these settings to connect and operate the database.

Full Transcript

To configure a database in Django, open the settings.py file in your project. Find the DATABASES dictionary. Set the 'ENGINE' key to specify which database type you want, like 'django.db.backends.sqlite3' for SQLite. Then set the 'NAME' key to the database name or file path. For databases like PostgreSQL, you also add USER, PASSWORD, HOST, and PORT. After saving these settings, run migrations to create the necessary tables in the database. This setup allows Django to connect and use the database for your app.

Practice

1. What is the purpose of the ENGINE setting in Django's database configuration?

easy

A. To define the path to the database file

B. To set the username for the database connection

C. To specify the type of database Django should use

D. To configure the database password

Solution

1. Step 1: Understand the role of ENGINE

   The ENGINE setting tells Django which database backend to use, like SQLite, PostgreSQL, or MySQL.

2. Step 2: Differentiate from other settings

   Settings like NAME, USER, and PASSWORD handle connection details, not the database type.

3. Final Answer:

   To specify the type of database Django should use -> Option C

4. Quick Check:

   ENGINE = database type [OK]

Hint: ENGINE always means database type, not credentials [OK]

Common Mistakes:

• Confusing ENGINE with NAME or USER
• Thinking ENGINE sets username or password
• Assuming ENGINE is a file path

2. Which of the following is the correct way to configure a SQLite database in Django's settings.py?

easy

A. """DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mydb' } }"""

B. """DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql', 'NAME': 'mydb' } }"""

C. """DATABASES = { 'default': { 'ENGINE': 'sqlite3', 'NAME': 'db.sqlite3' } }"""

D. """DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': BASE_DIR / 'db.sqlite3' } }"""

Solution

1. Step 1: Identify correct ENGINE for SQLite

   Django uses django.db.backends.sqlite3 as the ENGINE for SQLite databases.

2. Step 2: Check the NAME setting for SQLite

   The NAME should be a path to the SQLite file, commonly BASE_DIR / 'db.sqlite3' using pathlib.

3. Final Answer:

   DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': BASE_DIR / 'db.sqlite3' } } -> Option D

4. Quick Check:

   SQLite ENGINE = django.db.backends.sqlite3 [OK]

Hint: SQLite uses django.db.backends.sqlite3 and file path NAME [OK]

Common Mistakes:

• Using 'sqlite3' instead of 'django.db.backends.sqlite3'
• Confusing ENGINE with PostgreSQL or MySQL backends
• Setting NAME as just a string without path

3. Given this Django database configuration snippet, what database will Django connect to?

DATABASES = {
  'default': {
    'ENGINE': 'django.db.backends.postgresql',
    'NAME': 'myproject',
    'USER': 'admin',
    'PASSWORD': 'secret',
    'HOST': 'localhost',
    'PORT': '5432',
  }
}

medium

A. PostgreSQL database named 'myproject' on localhost

B. MySQL database named 'myproject' on localhost

C. SQLite database named 'myproject'

D. No database connection due to missing ENGINE

Solution

1. Step 1: Check the ENGINE setting

   The ENGINE is set to django.db.backends.postgresql, which means Django will use PostgreSQL.

2. Step 2: Identify database details

   The NAME is 'myproject', HOST is 'localhost', and PORT is '5432' which are typical PostgreSQL defaults.

3. Final Answer:

   PostgreSQL database named 'myproject' on localhost -> Option A

4. Quick Check:

   ENGINE = postgresql means PostgreSQL DB [OK]

Hint: ENGINE shows database type; PostgreSQL means option C [OK]

Common Mistakes:

• Assuming SQLite because of 'myproject' name
• Confusing PostgreSQL with MySQL
• Ignoring HOST and PORT settings

4. Identify the error in this Django database configuration:

DATABASES = {
  'default': {
    'ENGINE': 'django.db.backends.mysql',
    'NAME': 'mydb',
    'USER': 'root',
    'PASSWORD': 'pass123',
    'HOST': '',
    'PORT': '',
  }
}

medium

A. NAME must be a file path for MySQL

B. Empty HOST and PORT cause connection failure

C. PASSWORD cannot be empty string

D. ENGINE should be 'django.db.backends.postgresql'

Solution

1. Step 1: Check HOST and PORT values

   HOST and PORT are empty strings, which can cause connection issues because MySQL expects valid host and port or defaults.

2. Step 2: Understand default behavior

   Leaving HOST and PORT empty may work if MySQL uses defaults, but empty strings are not recommended and can cause errors.

3. Final Answer:

   Empty HOST and PORT cause connection failure -> Option B

4. Quick Check:

   HOST and PORT must be valid or omitted [OK]

Hint: Empty strings for HOST/PORT can break MySQL connection [OK]

Common Mistakes:

• Thinking empty strings mean localhost defaults
• Confusing ENGINE with PostgreSQL
• Assuming PASSWORD must be non-empty always

5. You want to configure Django to use PostgreSQL in production but SQLite in development. Which approach correctly handles this in settings.py?

hard

A. Use environment variables to switch ENGINE and NAME based on environment

B. Set ENGINE to PostgreSQL always and change NAME for dev and prod

C. Use SQLite ENGINE and change USER for production

D. Configure both databases in DATABASES and Django picks automatically

Solution

1. Step 1: Understand environment-based configuration

   Using environment variables lets you switch database settings without changing code, ideal for dev vs prod.

2. Step 2: Why other options fail

   Always setting PostgreSQL ENGINE won't work in dev without PostgreSQL installed; changing USER alone doesn't switch DB type; Django does not auto-pick between multiple databases without explicit routing.

3. Final Answer:

   Use environment variables to switch ENGINE and NAME based on environment -> Option A

4. Quick Check:

   Env vars enable flexible DB config [OK]

Hint: Use env vars to switch DB settings per environment [OK]

Common Mistakes:

• Hardcoding production DB in dev settings
• Assuming Django auto-selects DB from multiple configs
• Changing USER does not switch database type