Documentation Source Text: Check-in [26245406d3]

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.
Timelines:	family \| ancestors \| descendants \| both \| trunk
Files:	files \| file ages \| folders
SHA1:	26245406d34545c4760caef875dc50da94a616f4
User & Date:	drh 2016-02-15 15:45:19

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

Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/fts5.in.

  <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 ommitted. 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.

  <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.

  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.
}








>
>
>
>

  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.
}