Re:Django: One ORM to rule all databases
by sgarland on Sunday October 12, 2025 @10:40AM
(#45558546)
Alembic cannot fake a migration, which is a continual source of pain for me at my current job. There are many migrations that I simply don’t trust development teams to do. The inability to easily tell Alembic to get over itself and trust that something has occurred is frustrating.
[ Parent
| on HN ]
Re:Django: One ORM to rule all databases
by sonthonax on Sunday October 12, 2025 @11:25AM
(#45558863)
You just set the alembic version yourself in the alembic.version table. It’s not rocket science.
Re:Django: One ORM to rule all databases
by sgarland on Sunday October 12, 2025 @11:38AM
(#45559000)
Yes, I know how to fix it. I’m saying that it’s absurd to have to drop down to SQL to get an ORM to play nicely; Django handles this with a flag.
Re:Django: One ORM to rule all databases
by leetrout on Sunday October 12, 2025 @01:45PM
(#45560159)
That's fair. Especially in environments in 2025 where it's common to only care about a DB URL for the app config and pretty much never manually jump into the DB.
I run into this with lots of tools and I just shrug and move on... I've actually never given this a second thought until you pointed out this inconsistency.