Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix another typo on the news page. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
04b4ed6a0dc058c3fbb06711292179df |
User & Date: | drh 2011-12-19 22:02:02.224 |
Context
2011-12-19
| ||
22:08 | Use ^ instead of ^ in news articles since the rendering software strips out all ^ characters. (check-in: 0fb2011c18 user: drh tags: trunk) | |
22:02 | Fix another typo on the news page. (check-in: 04b4ed6a0d user: drh tags: trunk) | |
21:08 | Fix a typo. "no" becomes "now". (check-in: 2286e5b9c1 user: drh tags: trunk) | |
Changes
Changes to pages/news.in.
︙ | ︙ | |||
24 25 26 27 28 29 30 | Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, and 3.7.8 is optional. Upgrading from other versions is recommended. The [SQLITE_ENABLE_STAT2] compile-time option is now a no-op. The enhanced query-planner functionality formerly available using SQLITE_ENABLE_STAT2 is now available through [SQLITE_ENABLE_STAT3]. The enhanced query planning is still disabled by default. However, future releases of SQLite might | | | 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, and 3.7.8 is optional. Upgrading from other versions is recommended. The [SQLITE_ENABLE_STAT2] compile-time option is now a no-op. The enhanced query-planner functionality formerly available using SQLITE_ENABLE_STAT2 is now available through [SQLITE_ENABLE_STAT3]. The enhanced query planning is still disabled by default. However, future releases of SQLite might convert STAT3 from an enable-option to a disable-option so that it is available by default and is only omitted upon request. The [FTS4] full-text search engine has been enhanced such that tokens in the search string that begin with "^" must be the first token in their respective columns in order to match. Formerly, "^" characters in the search string were simply ignored. Hence, if a legacy application was including "^" characters in FTS4 search strings, thinking that they would |
︙ | ︙ |