Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Remove mention of the REVERSE collating sequence from the documentation. (CVS 3159) |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: | bd6876a1a946a9b266b31d776081464de7c7f437 |
| User & Date: | drh 2006-04-01 14:38:41 |
Context
|
2006-04-02
| ||
| 11:57 | Do not strip windows DLLs because this prevents them from being relocatable. Ticket #1474. (CVS 3160) check-in: 94054cd9 user: drh tags: trunk | |
|
2006-04-01
| ||
| 14:38 | Remove mention of the REVERSE collating sequence from the documentation. (CVS 3159) check-in: bd6876a1 user: drh tags: trunk | |
|
2006-03-29
| ||
| 00:24 | Properly record the names of triggers even if the name is quoted. Ticket #1737. (CVS 3158) check-in: 4ba280dd user: drh tags: trunk | |
Changes
Changes to www/datatype3.tcl.
1
2
3
4
5
6
7
8
...
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
|
set rcsid {$Id: datatype3.tcl,v 1.12 2006/01/26 13:25:08 danielk1977 Exp $}
source common.tcl
header {Datatypes In SQLite Version 3}
puts {
<h2>Datatypes In SQLite Version 3</h2>
<h3>1. Storage Classes</h3>
................................................................................
comparison is determined using memcmp(), regardless of the encoding of the
string. SQLite v3 provides the ability for users to supply arbitrary
comparison functions, known as user-defined collation sequences, to be used
instead of memcmp().
</p>
<p>
Aside from the default collation sequence BINARY, implemented using
memcmp(), SQLite features two extra built-in collation sequences
intended for testing purposes, NOCASE and REVERSE:
</p>
<UL>
<LI><b>BINARY</b> - Compares string data using memcmp(), regardless
of text encoding.</LI>
<LI><b>REVERSE</b> - Collate in the reverse order to BINARY. </LI>
<LI><b>NOCASE</b> - The same as binary, except the 26 upper case
characters used by the English language are
folded to their lower case equivalents before
the comparison is performed. </UL>
<h4>7.1 Assigning Collation Sequences from SQL</h4>
|
|
|
|
<
|
1
2
3
4
5
6
7
8
...
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
|
set rcsid {$Id: datatype3.tcl,v 1.13 2006/04/01 14:38:41 drh Exp $}
source common.tcl
header {Datatypes In SQLite Version 3}
puts {
<h2>Datatypes In SQLite Version 3</h2>
<h3>1. Storage Classes</h3>
................................................................................
comparison is determined using memcmp(), regardless of the encoding of the
string. SQLite v3 provides the ability for users to supply arbitrary
comparison functions, known as user-defined collation sequences, to be used
instead of memcmp().
</p>
<p>
Aside from the default collation sequence BINARY, implemented using
memcmp(), SQLite features one extra built-in collation sequences
intended for testing purposes, the NOCASE collation:
</p>
<UL>
<LI><b>BINARY</b> - Compares string data using memcmp(), regardless
of text encoding.</LI>
<LI><b>NOCASE</b> - The same as binary, except the 26 upper case
characters used by the English language are
folded to their lower case equivalents before
the comparison is performed. </UL>
<h4>7.1 Assigning Collation Sequences from SQL</h4>
|