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.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: dcc4d55e47196f509b66006f2864d5f3d5f4a22a6f419b46de479f76c24beeb2
User & Date: drh 2019-03-02 17:13:44
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
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/json1.in.

   172    172   store values that are NULL, integers, floating-point numbers, text,
   173    173   and BLOBs.  It is not possible to add a sixth "JSON" type.
   174    174   
   175    175   <p>
   176    176   The json1 extension does not (currently) support a binary encoding
   177    177   of JSON.  Experiments have been unable to find a binary encoding
   178    178   that is significantly smaller or faster than a plain text encoding.
   179         -(The present implementation parses JSON text at over 300 MB/s.)
          179  +(The present implementation parses JSON text at over 1 GB/s.)
   180    180   All json1 functions currently throw an error if any of their
   181    181   arguments are BLOBs because BLOBs are reserved
   182    182   for a future enhancement in which BLOBs will store the binary encoding
   183    183   for JSON.
   184    184   
   185    185   <p>
   186    186   The "1" at the end of the name for the json1 extension is deliberate.

Changes to pages/printf.in.

    94     94   Every IEEE-754 double can be represented exactly as a decimal floating-point
    95     95   value, but some doubles require more than 16 or 26 significant digits.
    96     96   
    97     97   <li><p>
    98     98   The order of the buffer pointer and buffer size parameters in the built-in
    99     99   snprintf() implementation is reversed from the order used in standard-library
   100    100   implementations.
          101  +
          102  +<li><p>
          103  +The built-in printf() implementation does not handle posix positional referencing
          104  +modifiers that allow the order of arguments to printf() to be different from the
          105  +order of the %-substitutions.  In the built-in printf(), the order of the arguments
          106  +must exactly match the order of the %-substitutions.
   101    107   </ol>
   102    108   
   103    109   <p>
   104    110   In spite of the disadvantages, the developers believe that having a built-in
   105    111   printf() implementation inside of SQLite is a net positive.
   106    112   
   107    113   <h1>Formatting Details</h1>