Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Updates to the README.txt file for ICU. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
d37443d33388b402e610a00c362a1e2e |
| User & Date: | drh 2010-07-30 00:31:08.000 |
Context
|
2010-07-30
| ||
| 05:06 | Add tests to check that the ICU regexp() function can only be called with exactly two arguments. (check-in: 451d965742 user: dan tags: trunk) | |
| 00:31 | Updates to the README.txt file for ICU. (check-in: d37443d333 user: drh tags: trunk) | |
|
2010-07-29
| ||
| 10:13 | Unconditionally include the pTmpSpace size in the estimate of the pager memory used. (check-in: 4b97f8640e user: drh tags: trunk) | |
Changes
Changes to ext/icu/README.txt.
| ︙ | ︙ | |||
135 136 137 138 139 140 141 |
always uses the built-in LIKE operator.
The ICU extension LIKE operator is always case insensitive.
3.2 The SQLITE_MAX_LIKE_PATTERN_LENGTH Macro
Passing very long patterns to the built-in SQLite LIKE operator can
| | | 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 |
always uses the built-in LIKE operator.
The ICU extension LIKE operator is always case insensitive.
3.2 The SQLITE_MAX_LIKE_PATTERN_LENGTH Macro
Passing very long patterns to the built-in SQLite LIKE operator can
cause excessive CPU usage. To curb this problem, SQLite defines the
SQLITE_MAX_LIKE_PATTERN_LENGTH macro as the maximum length of a
pattern in bytes (irrespective of encoding). The default value is
defined in internal header file "limits.h".
The ICU extension LIKE implementation suffers from the same
problem and uses the same solution. However, since the ICU extension
code does not include the SQLite file "limits.h", modifying
|
| ︙ | ︙ | |||
163 164 165 166 167 168 169 |
or other programming errors that could be exploited by a malicious
programmer.
If the ICU extension is used in an environment where potentially
malicious users may execute arbitrary SQL (i.e. gears), they
should be prevented from invoking the icu_load_collation() function,
possibly using the authorisation callback.
| < | 163 164 165 166 167 168 169 |
or other programming errors that could be exploited by a malicious
programmer.
If the ICU extension is used in an environment where potentially
malicious users may execute arbitrary SQL (i.e. gears), they
should be prevented from invoking the icu_load_collation() function,
possibly using the authorisation callback.
|