Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Use ^ instead of ^ in news articles since the rendering software strips out all ^ characters. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
0fb2011c1847315881bf990088add45a |
User & Date: | drh 2011-12-19 22:08:05.267 |
Context
2011-12-23
| ||
20:32 | Add the psow.html document describing powersafe overwrite. (check-in: 38fb9e5380 user: drh tags: trunk) | |
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) | |
Changes
Changes to pages/news.in.
︙ | ︙ | |||
28 29 30 31 32 33 34 | 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 | | | | | | 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 | 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 always be ignored, then those legacy applications might break with this update. The fix is simply remove the "^" characters from the search string. See the [version 3.7.9 | change summary] for additional changes associated with this release. } newsitem {2011-September-19} {Version 3.7.8} { |
︙ | ︙ |