Would it be realistic to pretend to use SQLite as a column-store database by leveraging ALTER TABLE ... ADD COLUMN massively and to expect better performance?
Suppose that instead of defining a table like CREATE TABLE (key, c1, c2, ... cn) I defined it as CREATE TABLE (key) followed by n-times "ALTER TABLE ... ADD COLUMN", for each column. Presumably when I query the table for a /key,column/ pair, SQLite will only need to access the storage area for /key/ and the storage area for /column/, and will not need to read the content of all the other columns?
