Unless you are talking about a column-store, most SQL databases fall to the same criticism; they are row-oriented with poor data locality.
Using column-oriented data is more that just a storage decision. It affects other parts of the language and especially your thought process and how you use the language.
Anybody who has used systems that are column (SoA) oriented understands this. And those that haven't all see to not understand how much it changes things.
Re:“What next?”
by AaronFriel on Sunday August 20, 2017 @02:57PM
(#15059731)
It is not what a relational database does (see another's reply on row-oriented vs column-oriented storage), but you miss the fact that this is fundamental for data locality in an application.
See, for example, this article on game design: http://gameprogrammingpatterns.com/data-locality.html
An SQL database is not just an object store.