Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add a news item for the 3.11.0 release. Fix a typo in the FTS5 documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
26245406d34545c4760caef875dc50da |
User & Date: | drh 2016-02-15 15:45:19.596 |
Context
2016-02-15
| ||
17:32 | Add the sha1sum and SQLITE_SOURCE_ID for version 3.11 to changes.html. (check-in: 850ce246dc user: dan tags: trunk) | |
15:45 | Add a news item for the 3.11.0 release. Fix a typo in the FTS5 documentation. (check-in: 26245406d3 user: drh tags: trunk) | |
2016-02-12
| ||
17:29 | Fix a typo in the cintro.html document. (check-in: 24a90038eb user: drh tags: trunk) | |
Changes
Changes to pages/fts5.in.
︙ | ︙ | |||
800 801 802 803 804 805 806 | <li> If the table is also a contentless table, the xInstCount, xInst, xPhraseFirst and xPhraseNext APIs behave as if the current row contains no phrase matches at all (i.e. xInstCount() returns 0). </ul> <p>If the detail option is set to <b>none</b>, then for each term the FTS index records just the rowid is stored. Both column and offset information | | | 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 | <li> If the table is also a contentless table, the xInstCount, xInst, xPhraseFirst and xPhraseNext APIs behave as if the current row contains no phrase matches at all (i.e. xInstCount() returns 0). </ul> <p>If the detail option is set to <b>none</b>, then for each term the FTS index records just the rowid is stored. Both column and offset information are omitted. As well as the restrictions itemized above for detail=column mode, this imposes the following extra limitations: <ul> <li> Column filter queries are not available. <li> Assuming the table is not also a contentless table, the <a href=#xPhraseFirstColumn>xPhraseFirstColumn</a> and <a href=#xPhraseNextColumn>xPhraseNextColumn</a> are slower than usual. |
︙ | ︙ |
Changes to pages/news.in.
︙ | ︙ | |||
14 15 16 17 18 19 20 21 22 23 24 25 26 27 | hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt regsub -all {[Tt]icket #(\d+)} $txt \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt hd_resolve "<blockquote>$txt</blockquote>" hd_puts "<hr width=\"50%\">" } newsitem {2016-01-20} {Release 3.10.2} { <p>Yikes! An optimization attempt gone bad resulted in a [https://www.sqlite.org/src/info/80369eddd5c94 | bug in the LIKE operator] which is fixed by this patch release. Three other minor but low-risk fixes are also included in the patch. } | > > > > | 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 | hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt regsub -all {[Tt]icket #(\d+)} $txt \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt hd_resolve "<blockquote>$txt</blockquote>" hd_puts "<hr width=\"50%\">" } newsitem {2016-02-15} {Release 3.11.0} { <p>SQLite [version 3.11.0] is a regularly scheduled maintenance release. } newsitem {2016-01-20} {Release 3.10.2} { <p>Yikes! An optimization attempt gone bad resulted in a [https://www.sqlite.org/src/info/80369eddd5c94 | bug in the LIKE operator] which is fixed by this patch release. Three other minor but low-risk fixes are also included in the patch. } |
︙ | ︙ |