Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Update the working on the "warning message" FAQ in response to complaints on the mailing list. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
cea598a713aac1c0eace162481c93fd7 |
| User & Date: | drh 2011-02-19 15:53:01.367 |
Context
|
2011-02-19
| ||
| 15:54 | Fix a typo on the change list for version 3.7.6. (check-in: b51db44405 user: drh tags: trunk) | |
| 15:53 | Update the working on the "warning message" FAQ in response to complaints on the mailing list. (check-in: cea598a713 user: drh tags: trunk) | |
|
2011-02-10
| ||
| 20:30 | Update the index page and the change log for 3.7.6. (check-in: a7fc545076 user: drh tags: trunk) | |
Changes
Changes to pages/faq.in.
| ︙ | ︙ | |||
433 434 435 436 437 438 439 | <p>Some people say that we should eliminate all warnings because benign warnings mask real warnings that might arise in future changes. This is true enough. But in reply, the developers observe that all warnings have already been fixed in the compilers used for SQLite development (various versions of GCC). Compiler warnings only arise from compilers that the developers do | | | 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 |
<p>Some people say that we should eliminate all warnings because
benign warnings mask real warnings that might arise in future changes.
This is true enough. But in reply, the developers observe that all
warnings have already been fixed in the
compilers used for SQLite development (various versions of GCC).
Compiler warnings only arise from compilers that the developers do
not use on a daily basis (Ex: MSVC).</p>
}
faq {
Case-insensitive matching of Unicode characters does not work.
} {
The default configuration of SQLite only supports case-insensitive
comparisons of ASCII characters. The reason for this is that doing
|
| ︙ | ︙ |