问题描述
如果一个关系数据库范例是以元组为导向的，我们在这里有最大的限制。
If one of relational databases paradigms is to be tuple oriented we have the biggest limitation here.
如果可以设计面向列的数据库， 。
矢量操作将执行开箱，索引，散列的简单符号列查找，链接列表作为引擎的幕后链接。
If one could design column oriented db, that would improve performance a lot.Vector operations would perform out of the box, indexing, hashing for simple symbol columns lookups, linked lists behind the scenes as engine.
内存映射：转储
仍然使用多个供应商支持的良好理解和标准语言（SQL）。
想象一下，可以设计多少工具
这不是更强壮（和KISS同时）？
Memory mapping: dumps in huge chunks in microseconds as well as loading those disk images.
And still have use well understood and standard language (SQL) that multiple vendors support.
Imagine how many tools could be designed for interfacing that thing, because of its simplicity.
Wouldn't it be more robust (and KISS at the same time)?
UPDATE
感谢所有参与者。
问题已被不公正地关闭，但我发现所有答案都非常有用。
UPDATE
Thanks to all contributors.
Question has been unjustly closed, though i've found your all answers very informative.
推荐答案
$ b b
否。它们是为特定任务设计的，比如OLTP vs OLAP。即使是像MySQL这样的流行软件也有列存储引擎（例如：）。
这里是一个有趣的阅读： （PDF格式）
Here's a potentially interesting read for you: C-Store: A Column-oriented DBMS (PDF format)
是一个面向数据仓库的流行的面向列的数据库， BI：
LucidDB is a popular column-oriented database for data warehousing and BI:
请参阅与您的兴趣重叠的功能列表：
See its list of features for those that overlap with your interests here: LucidDB Features
您可以使用SQL与LucidDB。
You can use SQL with LucidDB.
这篇关于是否所有现代RDBMS行定向？为什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！