On 04/21/2017 02:36 AM, Jonathan Gaillard wrote:
Here is the db https://ufile.io/q0314
Thanks for reporting this. It was a bug in the fts5 prefix query code.
Now fixed here:
http://www.sqlite.org/src/info/840042cb2bed2924
Dan.
If you do:
select rowid, name from filesfts where
Here is the db https://ufile.io/q0314
If you do:
select rowid, name from filesfts where filesfts match '"upload
file漢_5"*';
you get back:
141| upload file漢_5
142| upload file漢_6
152| upload file漢_5
153| upload file漢_6
163| upload file漢_5
164| upload file漢_6
174| upload file漢_5
175| upload
On 04/20/2017 07:11 AM, Jonathan Gaillard wrote:
If you do:
select rowid, name from filesfts where filesfts match '"upload
file漢_5"*';
This certainly seems like a bug. Are you able to share the database that
exhibits the problem?
Thanks,
Dan.
you get back:
141| upload file漢_5
If you do:
select rowid, name from filesfts where filesfts match '"upload
file漢_5"*';
you get back:
141| upload file漢_5
142| upload file漢_6
152| upload file漢_5
153| upload file漢_6
163| upload file漢_5
164| upload file漢_6
174| upload file漢_5
175| upload file漢_6
185| upload file漢_5
196| upload
On 04/18/2017 02:00 AM, Jonathan Gaillard wrote:
I have a db where I have a query returning results from something I believe is
deleted already from a FTS5 table. This is a normal FTS5 table, not a
contentless one so I used the normal DELETE.
Only after I run:
INSERT INTO
I have a db where I have a query returning results from something I believe is
deleted already from a FTS5 table. This is a normal FTS5 table, not a
contentless one so I used the normal DELETE.
Only after I run:
INSERT INTO MyFTSTable(MyFTSTable, rank) VALUES('automerge', 0);
INSERT INTO
6 matches
Mail list logo
