> Sent: Thursday, October 29, 2015 at 2:04 PM > From: "Paul Sanderson" <sandersonforensics at gmail.com> > To: "SQLite mailing list" <sqlite-users at mailinglists.sqlite.org> > Subject: Re: [sqlite] How would sqlite read this from disk? > > It reads a complete page at a time so there is no seeking other than > to the start of each row - in the sense of a disk seek. > > Note that there may be multiple required rows on the same page if the > row length is much less than the page length, or if rows are longer > than a size determined by some arcane math from the page size (see the > file format documentation), a row may overflow to one or more pages
Ah, so this is what I seem to have missed. The pages... This is unfortunate as the read-heavy application won't likely benefit from SQLite. Only a small fraction of the row data is used each query, and it seems like It'll have to read the entire row (via the page) each time? I wonder how much work it would be to come up with a "SQLite read-only mode" bypasses the page interface, but allows the SQL parser to query the data. it seems that pages are only needed when you're managing updates to the table. If you're write-once-query-forever it seems there would be tremendous performance gains to be had. Or is that just crazy talk?
