Re:Django and Postgres for the Busy Rails Developer
by kshahkshah on Wednesday December 11, 2024 @04:22PM
(#42393123)
That's curious to me honestly. I really prefer the ergonomics of Django's ORM compared to when I've had to use SQLAlchemy+Alembic in the past. I find alembic incredibly confusing and poorly documented. Not that documentation matters as much nowadays with AI
[ Parent
| on HN ]
Re:Django and Postgres for the Busy Rails Developer
by agumonkey on Wednesday December 11, 2024 @06:15PM
(#42394146)
yeah, alembic feels especially "small" and obscure compared to the hyper exhaustive nature of SQLA for everything else. felt like a side project at first
Re:Django and Postgres for the Busy Rails Developer
by gmassman on Wednesday December 11, 2024 @08:55PM
(#42395327)
Alembic is certainly a bit of a challenge to grasp at first, especially if you want to do anything more complicated than create or alter tables. However, it does provide a great amount of flexibility if you want to implement more complex migration functionality. It allows library developers to add powerful features that would be very difficult to do with Rails/ActiveRecord or Django ORM.
FWIW I maintain the flask-audit-logger package. It allows users to maintain audit logs of specific tables using postgres triggers. Being able to create custom migration operations is really an amazing feat. The alembic docs are quite dense, but the code is well organized and very readable.