still prohibited, however, since we do not want to delete a table out
from under an running query. (CVS 3902)
FossilOrigin-Name: 5b4bf1fce4d589337cfb1b46d75c751bbdc607d5
character immediately after the end of a term is '*', that term is
marked for prefix matching. Modify term comparison in
snippetOffsetsOfColumn() to respect isPrefix. fts2n.test runs prefix
searching through some obvious test cases. (CVS 3893)
FossilOrigin-Name: 7c4c65924035d9f260f6b64eb92c5c6cf6c04b7b
The new function docListUnion() is used to accumulate a union of the
hits for the matching terms, which will be merged across segments
using docListMerge(). (CVS 3891)
FossilOrigin-Name: 72c796307338c2751a91c30f6fb16989afbf3816
Also implement correct prefix-handling for traversal of interior nodes
of segment tree. A given prefix can span multiple children of an
interior node, and from there the branches need to be followed in
parallel. (CVS 3889)
FossilOrigin-Name: cae844a01a1d87ffb00bba8b4e7b62a92e633aa9
to sqlite3_prepare() where the nBytes parameter is positive but less than
the length of the input SQL string. (CVS 3888)
FossilOrigin-Name: 27bf3fc3cf3c9c7acdbf9281a4669c9f642b0097
search. Doclists from multiple prefix matches will need a union merge
function, which will have to logically happen across a segment before
doclists are merged between segments. (CVS 3887)
FossilOrigin-Name: 7ddb82668906e33e2d6a796f2da1795032e036d5
Previously, the code looped until the block was a leaf node as
indicated by a leading NUL. Now the code loops until it finds a block
in the range of leaf nodes for this segment, then reads it using
LeavesReader. This will make it easier to traverse a range of leaves
when doing a prefix search. (CVS 3884)
FossilOrigin-Name: 9466367d65f43d58020e709428268dc2ff98aa35
Prefix-searching will want to accumulate data across multiple leaves
in the segment, using LeavesReader instead of LeafReader is the first
step in that direction. (CVS 3881)
FossilOrigin-Name: 22ffdae4b6f3d0ea584dafa5268af7aa6fdcdc6e
call to sqlite3_value_blob(). Add documentation to explain this hazard.
Add many new tests. Ticket #2321. (CVS 3880)
FossilOrigin-Name: e92bd97a3726bbb7978489e2994747127c4aefcf
the library understands, make the database read-only. The old behavior
was to make the database unreadable. (CVS 3866)
FossilOrigin-Name: 10648e99929b4f640855433b6e47702687039286
the other, the code potentially tries to read past the end of the
doclist. http://www.sqlite.org/cvstrac/tktview?tn=2309 (CVS 3862)
FossilOrigin-Name: dfac6082e8ffc52a85c4906107a7fc0e1aa9df82
very difficult to devise a test case where it might lead to an unexpected
result. Ticket #2306. (CVS 3856)
FossilOrigin-Name: 7f9f0444ed1a85ed682b604fded535bff5be1535
not SQLITE_DONE. This fix only effects the legacy sqlite3_prepare()
interface. It already worked correctly with sqlite3_prepare_v2(). (CVS 3854)
FossilOrigin-Name: 165dc72d7024258e225c8a7d60118071282f0f44
