Re:Ask HN: Have you ever chosen Postgres over Mongo and regr...
by kevinoid on Tuesday July 10, 2018 @11:28AM
(#17498918)
Sure, but I found that I was wasting a lot of time writing dead-simple SQL queries and object mapping that could have been better spent writing application code (and was after switching to MongoDB).
[ Parent
| on HN ]
Re:Ask HN: Have you ever chosen Postgres over Mongo and regr...
by piva00 on Wednesday July 11, 2018 @04:00AM
(#17505211)
So instead of writing dead simple SQL queries (that mostly you could copy-paste if you don't want the complexity of dynamically generating them) it was easier and simpler to switch the whole data layer?
Re:Ask HN: Have you ever chosen Postgres over Mongo and regr...
by EpicEng on Tuesday July 10, 2018 @01:01PM
(#17499971)
Why wouldn't you auto generate the simple SQL stuff? It's a no brainier really. It's so easy to dynamically create simple selects, updates, etc.
Re:Ask HN: Have you ever chosen Postgres over Mongo and regr...
by kevinoid on Tuesday July 10, 2018 @01:47PM
(#17500466)
I played around with that a little, but it seemed like once you start trying to auto-generate SQL from objects you are basically writing a simple ORM. So you either spend time writing queries, spend time building an ORM, spend time fixing an existing ORM, or some combination of those.
Re:Ask HN: Have you ever chosen Postgres over Mongo and regr...
by EpicEng on Tuesday July 10, 2018 @04:41PM
(#17501949)
Sure, but it's about finding that sweet spot. I dislike large ORMs
The majority of queries are simple and trivial to auto generate. The more entities you add the more value you get from it.