2 ms·
> A lot of effort for not so much added value. It's not a lot of effort; in fact I'd argue it's free, or even negative cost. If you're in the habit of followin
by lmm 3y ago
> A lot of effort for not so much added value.
It's not a lot of effort; in fact I'd argue it's free, or even negative cost. If you're in the habit of following that paradigm then it's no harder than the mutate-everything-in-place paradigm.
> It’s also much easier/faster to calculate sums and statistics one one table column instead of doing many joins every time you need the price.
WTF? Did 1970 call and ask for their hardware back?
- hot_gril 3y ago> WTF? Did 1970 call and ask for their hardware back? The joins can actually get slow enough to matter for a UI. Depending on your use case, denormalized $ values can make total sense, but that should be separate from your properly normalized tables.
- andix 3y agoI've seen POS databases with millions of invoice positions. There is a substantial delay if you do 10 joins on a few million records. Calculating a sum over one column of millions of rows is substantially faster. It could be 2 seconds vs 200 seconds.