147
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Sep 2023
147 points (93.5% liked)
Programming
16670 readers
176 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Yeah, that's great, until you need to conditionally compose a query. Suddenly your pre baked queries are not enough. So you either:
You write like it's ORM vs native. ORMs let you write native queries and execute them while also doing all the tedious work for you such as:
So if you love native queries write native queries in an ORM which will do all the tedious shit for you.
Composable querying/pushdown is nice but transaction management is huge. It's not an easy task to correctly implement a way to share transactions between methods and between repository classes. But the alternative is, your transactions are limited to individual methods (or you don't use them, and you risk leaving your database in an inconsistent state without manual cleanup).
I agree. If you have a relational database and an object-oriented programming language you're going to have to map data one way or another.
That being said, using object-oriented doesn't necessarily mean the data abstraction needs to be objects too. Python is object-oriented yet Pandas is a very popular relational abstraction for it.
Parameterized queries are native to the database engine. They're going to be available regardless what you use on the client side.
(Well, if the database implements them... having flashbacks to back when MySQL didn't, and it taught a couple of generations of programmers extremely bad "sanitization" practices.)
Check out the active record pattern. It's a thin layer over SQL that lets you put together a query programatically (and nothing more).
This is very database specific and many ORMs don't do a great job of it. If anything this is a con for ORMs not a pro.
Again, very hit and miss. Each database has particular quirks and you need to know so much about them to use transactions effectively that it negates any insulation that the ORM provides.