Documentation Source Text

Check-in [dcc4d55e47]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Merge fixes from the 3.27 branch.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: dcc4d55e47196f509b66006f2864d5f3d5f4a22a6f419b46de479f76c24beeb2
User & Date: drh 2019-03-02 17:13:44.780
Context
2019-03-06
15:03
Merge changes from the 3.27 branch. (check-in: 00f74a59cd user: drh tags: trunk)
2019-03-02
17:13
Merge fixes from the 3.27 branch. (check-in: dcc4d55e47 user: drh tags: trunk)
17:12
Add an initial change log for the 3.28 development cycle. (check-in: f41d1a3db0 user: drh tags: trunk)
2019-03-01
13:27
Update the JSON parsing speed in the json1.html documentation. (check-in: 393a3d19ae user: drh tags: branch-3.27)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/json1.in.
︙︙
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186

store values that are NULL, integers, floating-point numbers, text,
and BLOBs.  It is not possible to add a sixth "JSON" type.

<p>
The json1 extension does not (currently) support a binary encoding
of JSON.  Experiments have been unable to find a binary encoding
that is significantly smaller or faster than a plain text encoding.
(The present implementation parses JSON text at over 300 MB/s.)
All json1 functions currently throw an error if any of their
arguments are BLOBs because BLOBs are reserved
for a future enhancement in which BLOBs will store the binary encoding
for JSON.

<p>
The "1" at the end of the name for the json1 extension is deliberate.








|








172
173
174
175
176
177
178
179
180
181
182
183
184
185
186

store values that are NULL, integers, floating-point numbers, text,
and BLOBs.  It is not possible to add a sixth "JSON" type.

<p>
The json1 extension does not (currently) support a binary encoding
of JSON.  Experiments have been unable to find a binary encoding
that is significantly smaller or faster than a plain text encoding.
(The present implementation parses JSON text at over 1 GB/s.)
All json1 functions currently throw an error if any of their
arguments are BLOBs because BLOBs are reserved
for a future enhancement in which BLOBs will store the binary encoding
for JSON.

<p>
The "1" at the end of the name for the json1 extension is deliberate.
︙︙
Changes to pages/printf.in.
︙︙
94
95
96
97
98
99
100






101
102
103
104
105
106
107

Every IEEE-754 double can be represented exactly as a decimal floating-point
value, but some doubles require more than 16 or 26 significant digits.

<li><p>
The order of the buffer pointer and buffer size parameters in the built-in
snprintf() implementation is reversed from the order used in standard-library
implementations.






</ol>

<p>
In spite of the disadvantages, the developers believe that having a built-in
printf() implementation inside of SQLite is a net positive.

<h1>Formatting Details</h1>








>
>
>
>
>
>








94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113

Every IEEE-754 double can be represented exactly as a decimal floating-point
value, but some doubles require more than 16 or 26 significant digits.

<li><p>
The order of the buffer pointer and buffer size parameters in the built-in
snprintf() implementation is reversed from the order used in standard-library
implementations.

<li><p>
The built-in printf() implementation does not handle posix positional referencing
modifiers that allow the order of arguments to printf() to be different from the
order of the %-substitutions.  In the built-in printf(), the order of the arguments
must exactly match the order of the %-substitutions.
</ol>

<p>
In spite of the disadvantages, the developers believe that having a built-in
printf() implementation inside of SQLite is a net positive.

<h1>Formatting Details</h1>
︙︙