Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Migrations Under The Hood
Search
Andrew Godwin
November 14, 2014
Programming
13k
6
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Migrations Under The Hood
A talk I gave at Django Under The Hood 2014.
Andrew Godwin
November 14, 2014
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
410
Django Through The Years
andrewgodwin
0
330
Writing Maintainable Software At Scale
andrewgodwin
0
540
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
430
Async, Python, and the Future
andrewgodwin
2
750
How To Break Django: With Async
andrewgodwin
1
840
Taking Django's ORM Async
andrewgodwin
0
860
The Long Road To Asynchrony
andrewgodwin
0
780
The Scientist & The Engineer
andrewgodwin
1
860
Other Decks in Programming
See All in Programming
AIエージェント時代のコードレビューを設計する
nogu66
6
2.5k
AIを上手に使っていこうとしたら越境せざるを得なくなった話 〜実践1年で見えた境界を越えなければならない理由と進め方〜 / Crossing borders with AI
tomoyakitaura
3
1k
LLMは4年分のCompose移行を再現できるのか?実プロダクト279件のXMLで探る自動化の境界線
makun
0
420
MySQLとPostgreSQLって何が違うの?
akagami
PRO
0
170
【デモ】Kiroで体験する仕様駆動開発|設計からコーディングまでAIと進める開発フロー
cmkudo
0
580
コンパウンドプロダクト開発のためのローカルプロセスマネージャー再発明 #layerxgo
izumin5210
0
640
AIと壁打ちしながら進めるコスト管理
fufuhu
2
1.9k
DynamoDBの基礎を振り返りながらベクトル検索機能を理解する
musan
3
270
AI時代に学ぶ 好きなルール 嫌いなルール Linter編
shorty5121
0
860
MIZARU@SPAJAM2026 第二回予選
1901drama
0
110
The Good Stuff, Not the Slop: Engineering High-Quality Android Apps with Modern AI Tooling
danybony
1
190
Hello, Hiroshima Geospatial Data! — Exploring DoboX with Python
ra0kley
0
170
Featured
See All Featured
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
6.1k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
16k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
49
10k
Winning Ecommerce Organic Search in an AI Era - #searchnstuff2025
aleyda
1
2.1k
We Are The Robots
honzajavorek
0
340
How to Think Like a Performance Engineer
csswizardry
28
2.8k
Ruling the World: When Life Gets Gamed
codingconduct
0
320
Introduction to Domain-Driven Design and Collaborative software design
baasie
1
970
How to Grow Your eCommerce with AI & Automation
katarinadahlin
PRO
1
260
The Pragmatic Product Professional
lauravandoore
37
7.4k
How to build an LLM SEO readiness audit: a practical framework
nmsamuel
1
890
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
508
140k
Transcript
Migrations UNDER THE HOOD Andrew Godwin Migrations
Andrew Godwin Author of South migrations library Hi, I'm Author
of 1.7 Django migrations Senior Software Engineer at Eventbrite Apparently at every Django conference
Migrations
Migrations
Other talks are available. This is a technical dive!
The Initial Plan Django Schema backend ORM Hooks South 2
Migration handling User interface
TheBRevisedBPlan Django SchemaBbackend ORMBHooks SouthB2 MigrationBhandling UserBinterface BackportBforB1.4B-B1.6
The Revised Revised Plan Django Schema backend ORM Hooks Migration
handling User interface
Logically Separate SchemaEditor Schema Migrations field.deconstruct() ModelOptions.apps Operations Loader /
Graph Executor Autodetector Optimiser State
Logically Separate SchemaEditor Schema Migrations field.deconstruct() ModelOptions.apps Operations Loader /
Graph Executor Autodetector Optimiser State
myapp/0001 myapp/0002 otherapp/0001 contenttypes/0001 appthree/0001 myapp/0003 otherapp/0002
(insert wavy memory effect!) Why do we need dependencies?
Makes all tables syncdb Sets all constraints Adds all ForeignKeys
Makes appA tables migrations Makes appB tables Adds FKs from
appB to appA Adds FKs from appA to appB
Makes appA tables migrations Makes appB tables Adds FKs from
appB to appA Adds FKs from appA to appB
The obvious stuff. Basic Dependencies
Or your database gets really mopey. FK target add before
FK added
In the general case; some DBs less fussy FK target
delete after FK deleted
Good luck doing it otherwise. Model create before field create
Also after field create Model delete after field alter
Stuff you occasionally forget Django has. Trickier Dependencies
And, of course, the reverse for deletion. M2M through model
before M2M
I'll let you figure out deletion reversals from now on.
MTI parent before MTI child
Index together, too Unique together after fields
Well done if you've actually used this feature. Order with
respect to after target
This happens when you turn proxies into real models. Same
delete before same create
Impossible dependencies
OH PLEASE NO TAKE IT AWAY Swappable models
Your migration dependencies myapp/0001 myapp/0002 otherapp/0001 auth/0001 contenttypes/0001
myapp/0001 myapp/0002 otherapp/0001 auth/0001 contenttypes/0001 thirdapp/0001 Your migration dependencies on
swappable models
what? Your migration dependencies on swappable models myapp/0001 myapp/0002 otherapp/0001
auth/0001 contenttypes/0001 thirdapp/0001 ???
what? Your migration dependencies on swappable models myapp/0001 myapp/0002 otherapp/0001
auth/0001 contenttypes/0001 thirdapp/0001 ??? argh
End of presentation. Click to exit.
They can't change at runtime, for swappable models or anything
else. Dependencies are static
(for a while, the answer was "careful function ordering") How
is it implemented?
no issues depend match shift operations restart
Using dependencies to define boundaries Chop operations into migrations
Optimisation
There's really quite a lot. Even more rules
create model + delete model = nothing create model +
create field = create model create field + alter field = create field alter field + delete field = delete field alter field + alter field = alter field
This time, with collapses rather than swaps Even more shuffling
can't reduce reduce possible check conflicts reduced, reset
Lets us be more verbose and clear with operations Applied
after autodetection
Makes your history a bit shorter Applied after squash
Loading & Graph
Builds graph of all basic migrations in memory Loads from
disk first
Marks applied state on each node Loads from db second
Only if all replaced nodes have same applied state Applies
squashes third
In-order list of all a node's ancestors in the tree
Graph returns "plans"
• Autodetector is slow • Optimizer is not great •
Graph state building is inefficient Room for improvement!
django/db/migrations/autodetector.py Autodetector django/db/migrations/optimizer.py Optimiser reduce()GfunctionGisGentryGforGlogic StartGatG_detect_changes()GandGfollowGcalls django/db/migrations/graph.py Graph django/db/migrations/loader.py
Thank you. Andrew Godwin @andrewgodwin