It seems to me that article is written by a guy who has a lot of
knowledge of the database engine and has some issues (mostly) with
Django migrations system. His solution to the problem is to use direct
SQL statements which of course can be more finely controlled than
whatever Django creates.
While I agree with some of the author's points, I think a critical piece of
context is that Django migrations are designed for the 90% case - i.e., people
who just want something to work on a small scale and don't need to worry about
many aspects of the database yet.
Like all parts of Django,
HI all,
I would suggest reading this interesting article by Daniele Varrazzo
(the maintainer of psycopg2 and creator of psycopg3) on Django
migrations.
It contains some criticisms but I also think some interesting hints
for improving Django ORM :
