Documentation Source Text

Check-in [b22a695db2]
Login

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

Overview
Comment:Update the change log with more details of recent enhancements.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: b22a695db242bb8918d8fa6d43877de3f78bf6623e71d82828a64236d7d432d2
User & Date: drh 2017-10-30 17:32:01.629
Context
2017-11-03
02:37
Fix typo reported on the mailing list. (check-in: d26d101c74 user: mistachkin tags: trunk)
2017-10-30
17:32
Update the change log with more details of recent enhancements. (check-in: b22a695db2 user: drh tags: trunk)
2017-10-28
20:58
Preliminary changes for the 3.22.0 release. (check-in: b3e5268a9a user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/changes.in.
︙︙
18
19
20
21
22
23
24
25










26
27
28
29
30
31
32

  global nChng aChng xrefChng
  set aChng($nChng) [list $date $desc $options]
  set xrefChng($date) $nChng
  incr nChng
}

chng {2018-01-04 (3.22.0)} {
<li> Query planner enhancements (details pending)










}

chng {2017-10-24 (3.21.0)} {
<li> Take advantage of the atomic-write capabilities in the 
     [https://en.wikipedia.org/wiki/F2FS|F2FS filesystem] when available, for
     greatly reduced transaction overhead.  This currently requires the
     [SQLITE_ENABLE_BATCH_ATOMIC_WRITE] compile-time option.








|
>
>
>
>
>
>
>
>
>
>








18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

  global nChng aChng xrefChng
  set aChng($nChng) [list $date $desc $options]
  set xrefChng($date) $nChng
  incr nChng
}

chng {2018-01-04 (3.22.0)} {
<li> Query planner enhancements.
<ol type='a'>
  <li> The optimization of using an index to quickly compute an
       aggregate min() or max() is extended to work with
       [indexes on expressions].
  <li> The decision of whether to implement a FROM-clause subquery
       as a co-routine or using query flattening now considers whether
       the result set of the outer query is "complex" (if it
       contains functions or expression subqueries).  A complex result
       set bias the decision toward the use of co-routines.
</ol>
}

chng {2017-10-24 (3.21.0)} {
<li> Take advantage of the atomic-write capabilities in the 
     [https://en.wikipedia.org/wiki/F2FS|F2FS filesystem] when available, for
     greatly reduced transaction overhead.  This currently requires the
     [SQLITE_ENABLE_BATCH_ATOMIC_WRITE] compile-time option.
︙︙