Documentation Source Text

Check-in [ace42c454f]
Login

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

Overview
Comment:Merge branch-3.32 fixed into trunk.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: ace42c454fe63098d0eddb4f2b387575016454c6e40befb5c052d609cda4383f
User & Date: drh 2020-07-26 16:11:05
Context
2020-07-28
17:30
Update the change log for the unlocked-recovery enhancement. (check-in: 77c08efc0e user: drh tags: trunk)
2020-07-26
16:11
Merge branch-3.32 fixed into trunk. (check-in: ace42c454f user: drh tags: trunk)
16:08
On the download page, use sha3 instead of sha1. And deemphasize the text. (Leaf check-in: 0de47c19a5 user: drh tags: branch-3.32)
13:35
Improved wording of the floatingpoint.html document. (check-in: 010e930cc2 user: drh tags: trunk)
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/download.in.

38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
..
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
      set version 3.$m1.$m2
      if {$patch>0} {
        append version .$m3
      }
    }
    if {$datetag=="" && [regexp DATETAG $desc]} continue
    set size [file size $file]
    set sha1sum [lindex [exec sha1sum $file] 0]
    set units bytes
    if {$size>1024*1024} {
      set size [format %.2f [expr {$size/(1024.0*1024.0)}]]
      set units MiB
    } elseif {$size>1024} {
      set size [format %.2f [expr {$size/(1024.0)}]]
      set units KiB
................................................................................
    set href(a$href_cnt) $file
    hd_puts "<a id='a$href_cnt' href='hp1.html'>[file tail $file]</a><br>($size $units)</td>\n"
    hd_puts "<td width=\"5\"></td>"
    regsub -all VERSION $desc $version d2
    regsub -all DATETAG $d2 $datetag d2
    hd_puts "\n<td valign=\"top\">"
    hd_resolve [string trim $d2]
    hd_puts "<br>(sha1: $sha1sum)</td></tr>\n"
    incr ::nDownload
    if {$disable_flag} {
      set ::disable_more 1
    }
  }
  if {$frag!=""} {
    eval hd_keywords [lrange $frag 1 end]







|







 







|







38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
..
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
      set version 3.$m1.$m2
      if {$patch>0} {
        append version .$m3
      }
    }
    if {$datetag=="" && [regexp DATETAG $desc]} continue
    set size [file size $file]
    set sha3sum [lindex [exec fossil sha3sum $file] 0]
    set units bytes
    if {$size>1024*1024} {
      set size [format %.2f [expr {$size/(1024.0*1024.0)}]]
      set units MiB
    } elseif {$size>1024} {
      set size [format %.2f [expr {$size/(1024.0)}]]
      set units KiB
................................................................................
    set href(a$href_cnt) $file
    hd_puts "<a id='a$href_cnt' href='hp1.html'>[file tail $file]</a><br>($size $units)</td>\n"
    hd_puts "<td width=\"5\"></td>"
    regsub -all VERSION $desc $version d2
    regsub -all DATETAG $d2 $datetag d2
    hd_puts "\n<td valign=\"top\">"
    hd_resolve [string trim $d2]
    hd_puts "<br><small style='color: #999;'>(sha3: $sha3sum)</small></td></tr>\n"
    incr ::nDownload
    if {$disable_flag} {
      set ::disable_more 1
    }
  }
  if {$frag!=""} {
    eval hd_keywords [lrange $frag 1 end]

Changes to pages/quirks.in.

214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
<p>
In the query above, the values for the first_name and last_name columns
will correspond to the row that satisfied the max(salary) condition.

<li><p>
If a query contains no aggregate functions at all, then a GROUP BY
clause can be added as a substitute for the DISTINCT ON clause.  In other words,
output rows are filtered so that only one row is shows for each distinct
set of values in the GROUP BY clause.  If two or more output rows would
have otherwise had the same set of values for the GROUP BY columns, then
one of the rows is chosen arbitrarily.  (SQLite supports DISTINCT but not
DISTINCT ON, whose functionality is provided instead by GROUP BY.)
</ol>

<h1>Does Not Do Full Unicode Case Folding By Default</h1>







|







214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
<p>
In the query above, the values for the first_name and last_name columns
will correspond to the row that satisfied the max(salary) condition.

<li><p>
If a query contains no aggregate functions at all, then a GROUP BY
clause can be added as a substitute for the DISTINCT ON clause.  In other words,
output rows are filtered so that only one row is shown for each distinct
set of values in the GROUP BY clause.  If two or more output rows would
have otherwise had the same set of values for the GROUP BY columns, then
one of the rows is chosen arbitrarily.  (SQLite supports DISTINCT but not
DISTINCT ON, whose functionality is provided instead by GROUP BY.)
</ol>

<h1>Does Not Do Full Unicode Case Folding By Default</h1>