Hello Warren,
>author="Warren Young" >On Mar 28, 2018, at 5:51 AM, rene <RZaumseil@> wrote: >> >>> I’m suggesting that you don’t use SQLite’s JSON features at all. >> >> Oh no. Either I use the C++ parser or I use sqlite. > > >I’m suggesting that you do both: Parse the JSON with C++, then insert it in normalized SQL form into >SQLite, then query the data with pure ANSI SQL-92. > >If you absolutely need JSON querying at the SQLite level, you can split the difference: > > CREATE TABLE arrayname ( > id INTEGER NOT NULL PRIMARY KEY, > name TEXT NOT NULL, > json TEXT NOT NULL DEFAULT ‘' > ); > >Parse the id and name column values from the JSON text, then insert the JSON text and the parsed >values into the table. Now you can key off off the id and/or name, so you needn’t do a full table scan >even when querying fields of a specific JSON object, if you can address it by ID and/or name. Yes, you are right. And I have an offline translated sqlite database for testing. It's fast. And I would love to use it. I'm not inclined to use json. But people here have decided to use json. And I'm stuck with it. I was only trying to get faster then the already used C++ parser. One way was to use sqlite's json parser. When I could find a way to convert all the json in sql tables in time, fine. >> The C++ parser has no knobs to tune. > >Why do you need knobs? What specific benefit do you get from these knobs? To make is faster in "my" use case :) Thank you for your answer. Rene -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
