4 ms·
Slightly different topic, but there is value in using a column based ORM strategy where each attribute has it's own table, and objects are dispersed over the ta
by toolslive 8y ago
Slightly different topic, but there is value in using a column based ORM strategy where each attribute has it's own table, and objects are dispersed over the tables. It's very flexible and most of the time you just want a few objects with a certain attribute having a certain value anyway.
- phaedrus 8y agoSounds a lot like the array-of-structs vs struct-of-arrays design decision for game engines. One of the features Jonathan Blow put into the programming language he has been working on (JAI) is better support for this dichotomy. IMO most programming languages have optimized the language only for array of structs and historically all but ignored the struct of arrays case.
- toolslive 8y agoyes, and it has the same performance implications (struct-of-arrays performs better as it yields better locality when iterating over the fields)