Documentation errors: https://www.sqlite.org/draft/vtab.html#epovtab
In the 1.1.2 Eponymous virtual tables section (auxiliary word): "Note that SQLite versions prior to 3.8.12 did not check the xCreate method for NULL *before to* invoking it..." ------------------------------- https://www.sqlite.org/draft/json1.html under 2.0 Interface overview (missing word: "to") Backwards compatibility constraints mean that SQLite is only able to store values that are NULL, integers, floating-point numbers, text, and BLOBs. It is not *possible add* a sixth "JSON" type. ------------------------------- under 2.0 still - last paragraph (grammar: Starting a sentence with But): "...experience is gained, some kind of JSON extension might be folded into the SQLite core. But for now, JSON support remains an extension." Possible alternates: "...experience is gained, some kind of JSON extension might be folded into the SQLite core, but for now, JSON support remains an extension." "...experience is gained, some kind of JSON extension might be folded into the SQLite core. For now, JSON support remains an extension." ------------------------------- under 2.3 VALUE arguments, 1st paragraph (grammar - singular verb on plural noun) "Even if the input /value/ *strings looks* like well-formed JSON, they are still interpreted as..." ------------------------------- under 2.3 VALUE arguments, 3rd paragraph (grammar + punctuation) "For example, in the following call to json_object(), the /value/ argument looks like a well-formed JSON array. But because it is just ordinary SQL text it is interpreted as a literal..." Possible alternate: "For example, in the following call to json_object(), the /value/ argument looks like a well-formed JSON array*, but* because it is just ordinary SQL *text,* it is interpreted as a literal..." ------------------------------- Cheers, Ryan
