On 20 Jun 2017, at 2:34, Jens Alfke wrote: > My understanding from reading the docs is that SQLite view’s aren’t “built” > at all: their contents have no physical existence in the database, the views > are simply macros that transform the statements that use them. (Correct me if > I’m wrong; I haven’t actually used views.)
Hi, yes, that's right. That's why it makes sense to speed up VIEW execution as it's run dynamically when views are used. > You can create indexes to support JSON1 queries by using the same json_xx > function calls in a CREATE INDEX statement. Ah, cool. 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? -- Robert M. Münch, CEO M: +41 79 65 11 49 6 Saphirion AG smarter | better | faster http://www.saphirion.com http://www.nlpp.ch
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
