Why ORM maps Python to database in Django - Visual Breakdown

Concept Flow - Why ORM maps Python to database

Define Python class

↓

ORM reads class

↓

Create database table

↓

Create Python object instance

↓

ORM converts object to SQL INSERT

↓

Data saved in database

↓

Query database with ORM

↓

ORM converts SQL result to Python objects

This flow shows how ORM takes Python classes and objects, turns them into database tables and rows, and back again, so you work only in Python.

Execution Sample

Django

from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)

book = Book(title='My Book')
book.save()

Defines a Book class, creates an instance, and saves it to the database using ORM.

Execution Table

Step	Action	Python State	Database Action	Result
1	Define Book class	Book class with title field	No DB action yet	Class ready for ORM
2	Create Book instance	book.title = 'My Book'	No DB action yet	Object created in memory
3	Call book.save()	book object	Generate SQL INSERT	Prepare to save data
4	Execute SQL INSERT	book object	Insert row into book table	Data saved in DB
5	Query book table	No Python object yet	Generate SQL SELECT	Fetch data from DB
6	ORM converts result	Create Book objects from rows	No DB action	Python objects ready

💡 All Python objects are synced with database rows via ORM mapping

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 6
Book class	Defined	Defined	Defined	Defined
book instance	None	title='My Book'	title='My Book'	title='My Book'
Database rows	Empty	Empty	One row with title='My Book'	One row with title='My Book'

Key Moments - 2 Insights

Why don't we write SQL directly when using ORM?

Because ORM automatically converts Python objects to SQL commands, so you can work only in Python as shown in steps 3 and 4 of the execution_table.

How does ORM know what database table to use?

ORM reads the Python class definition (step 1) and creates or uses a matching database table, linking class fields to table columns.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 4?

A SQL INSERT command runs to save data

B Python object is deleted

C Python creates a new class

D Database table is dropped

💡 Hint

Check the 'Database Action' column at step 4 in execution_table

At which step does ORM convert database rows back to Python objects?

A Step 2

B Step 4

C Step 6

D Step 1

💡 Hint

Look at the 'Result' column for step 6 in execution_table

If you change the Book class fields, what part of the flow changes?

A Step 3 only

B Step 1 and database table structure

C Step 5 only

D No change at all

💡 Hint

Refer to concept_flow where class definition affects database table creation

Concept Snapshot

ORM maps Python classes to database tables.
You define models as Python classes.
ORM creates tables and columns automatically.
Saving objects runs SQL INSERT behind scenes.
Querying returns Python objects, not raw SQL.
This lets you work only in Python, no SQL needed.

Full Transcript

ORM stands for Object-Relational Mapping. It connects Python code to the database. First, you define a Python class representing your data. The ORM reads this class and creates a matching database table. When you create an object of this class and save it, ORM converts it into an SQL INSERT command to store data in the database. Later, when you query the database, ORM converts the SQL results back into Python objects. This way, you only write Python code and ORM handles the database communication for you.