> On Jun 20, 2017, at 12:48 AM, Robert M. Münch <robert.mue...@saphirion.com> > wrote: > > Since at one point I know all the columns and later on a couple columns could > be added, I'm thinking about creating the table with the known columns in a > classical way and have one additional JSON column for future expansion. I > think that could speed things up. What do you think?
Creating indexes on the JSON properties is the big optimization. What you’re proposing above will add a little extra performance, but I don’t think it’ll be that much (basically you’d just save the overhead of reading the property out of the JSON at the time the index is updated and when the query runs.) —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
