From de1caa20c41f730e54fb6974ba7821fe48816e40 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 13 Apr 2024 16:07:37 +0200 Subject: Adding upstream version 3.45.2. Signed-off-by: Daniel Baumann --- www/json1.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'www/json1.html') diff --git a/www/json1.html b/www/json1.html index a3f10da..7e15bc0 100644 --- a/www/json1.html +++ b/www/json1.html @@ -395,7 +395,7 @@ internal "parse tree" representation of JSON to be stored on disk, as a BLOB, in a format that we call "JSONB". By storing SQLite's internal binary representation of JSON directly in the database, applications can bypass the overhead of parsing and rendering JSON when reading and -updating JSON values. The internal JSONB format is also uses slightly +updating JSON values. The internal JSONB format also uses slightly less disk space then text JSON.

@@ -653,7 +653,7 @@ for infinity and not-a-number.

Most JSON functions do their internal processing using JSONB. So if the -input is text, they first most translate the input text into JSONB. +input is text, they first must translate the input text into JSONB. If the input is already in the JSONB format, no translation is needed, that step can be skipped, and performance is faster. @@ -698,7 +698,7 @@ text JSON when cast to text, then it is accepted as text JSON. This is actually a long-standing bug in the original implementation that the SQLite developers were unaware of. The documentation stated that a BLOB input to a JSON function should raise an error. But in the -actually implementation, the input would be accepted as long +actual implementation, the input would be accepted as long as the BLOB content was a valid JSON string in the text encoding of the database. @@ -1616,5 +1616,5 @@ SELECT DISTINCT json_extract(big.json,'$.id') WHERE json_tree.key='uuid' AND json_tree.value='6fa5181e-5721-11e5-a04e-57f3d7b32808'; - +

This page last modified on 2024-03-06 20:59:22 UTC

-- cgit v1.2.3