3 ms·
Putting aside performance implications, I get kinda irritated by having to do joins for basic queries all the time.
by zeroCalories 1y ago
Putting aside performance implications, I get kinda irritated by having to do joins for basic queries all the time.
- sgarland 1y agoThen don't use a relational database. Sorry for being rude, but joins are an integral part of the relational model. If you want a KV store, you should use a KV store; if you want a Document DB, you should use a Document DB.
- zeroCalories 1y agoSometimes I just wanna do some adhoc analysis and I need to do like four joins because some monkey decided to split everything into it's own table without thinking about the people that would actually have to use the db.
- sgarland 1y agoYour one-off analysis doesn’t trump the normal OLTP workloads.
- zeroCalories 1y agoI regularly have to do queries. I'm trying to understand my non-trivial product to figure out what work items will have, or have had, impact. Sometimes I'm in a meeting and need to do some real time analysis. My ability to understand and use the data is actually more important than a slightly higher database bill. And I thought we were ignoring the poor performance of normalization?
- datadrivenangel 1y agoIf you're doing reporting, create a reporting view that does all those joins once!