On 2018/03/28 2:34 PM, rene wrote:
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.
Ah, a shotgun-marriage to a wrongful ideal. Are you working at Micro$oft by any chance? :)
I was only trying to get faster then the already used C++ parser. One way was to use sqlite's json parser.
I can vouch to you that all of the SQLite code is made with great attention to efficiency, but even so, there is no real evidence or reason why it should be any faster than whatever other native-code JSON parser you are using. Even with the knobs, I would be surprised if you find a knob setting that significantly increases the SQLite parser speed over what you have. (And if you do, we'd like to know please!)
I'm sorry to hear you are stuck with it. Perhaps your JSON data has a definitive or specific format that is always the same? Perhaps the fields are always used? If so you can write a better parser than anyone else so long as those rules are adhered to.
Also, you may not be able to NOT use the JSON data, but are you allowed to add other columns (perhaps indexed ones) that could at least make some queries faster? Short of that, you have no real hope of more speed.
Good luck! Ryan _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
