3 ms·
Ehh, Django ORM always was one of the worst parts of Django.
by murkt 3y ago
Ehh, Django ORM always was one of the worst parts of Django.
- mrweasel 3y agoTrue, but it's the best ORM currently available for any language. It might not be the fastest, but it is the one that's has the highest level of developer comfort. Using Django is probably the reason why I can stand using SQLAlchemy, it's way to complicated for everything I do and it's just not a nice an experience.
- DeathArrow 3y ago>True, but it's the best ORM currently available for any language. Better than Entity Framework? Consider me impressed.
- mrweasel 3y agoDepending on what you consider important, and I haven't used Entity since... 2010 I think. For me, those two doesn't compare, the simplicity of the Django ORM makes Entity look dated, complex, like something out of the mainframe era. Entity is way more flexible, in the sense that you can use in any .Net project really. The Django ORM have no value outside Django, I have yet to anyone use just the ORM, without the rest of the framework.
- fomine3 3y agoEarly EF was GUI based complex one. Recent version is fine after they support "Code-first" API.
- cosmic_quanta 3y ago> True, but it's the best ORM currently available for any language. Such a strong assertion! I've used multiple ORMs (not Django's), including some of Haskell's type-safe ORMs (e.g. Persistent and Beam). I could not imagine going back. What makes Django's ORM so great?
- roflyear 3y agoHave you used SQLAlchemeny and PeeWee extensively? I have found these to be pretty fair when compared to Django. Anyway, you can use the Django ORM without Django :)
- murkt 3y agoI am not a fan of ORMs personally, so haven’t tried lots of them. But even in Python, SQLAlchemy is way better than Django ORM. Django ORM is tolerable on small projects, and quickly gets in the way on anything a bit more complicated.