adf52ce14b
We handle an UPDATE to a row by performing an UPDATE on the content table and by building new position lists for each term which appears in either the old or new versions of the row. We write these position lists all at once; this is presumably more efficient than a delete followed by an insert (which would first write empty position lists, then new position lists). (CVS 3434) FossilOrigin-Name: 757fa22400b363212b4d5f648bdc9fcbd9a7f152 |
||
---|---|---|
.. | ||
fts1 | ||
README.txt |
Version loadable extensions to SQLite are found in subfolders of this folder.