> > > Would be nice to have ability to store both key and payload in the > > index. (Let's call it index-only table) > > This could be a feature that sets some limitations on a table, like > > being unable to have more than one index or inefficient table scans, > > but it will also give some advantage in special cases like mine. > > What you're describing sounds very much to me like a SQLite table. See > http://www.sqlite.org/fileformat2.html, section 1.5, the reference to > "index b-tree". > > You're in good company. The technique of storing key and value together > "in order" in some sense is as old as databases. > > --jkl
So, to be clear, WITHOUT ROWID table will have it's PRIMARY KEY as a replacement for ROWID and table itself is an index? If so, it perfectly matches my needs. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
