I don't know if it makes any difference...but I think you want some quotes in your match... MATCH '"bug report API_Version:374" OR "API_Version:UAR"' 2nd set of quote is needed as it appears a semicolon has special meaning to "match". You can see the offset are different if you don't quote it... sqlite> select offsets(data) from data where data match '"bug report API_Version:374" OR "API_Version:UAR"'; 0 0 7 3 0 1 11 6 0 2 18 3 0 3 22 7 0 4 30 3 0 5 7 3 0 6 11 7 0 7 19 3 sqlite> select offsets(data) from data where data match '"bug report API_Version :374" OR API_Version:UAR'; 0 0 7 3 0 1 11 6 0 2 18 3 0 5 18 3 0 3 22 7 0 6 22 7 0 4 30 3 0 5 7 3 0 6 11 7 0 7 19 3 sqlite> select offsets(data) from data where data match '"bug report API_Version :374" OR API_Version:UAR'; And how come I don't see the RANK() function in my 3.7.4? I can't even find it in the code. Is that something you added? Michael D. Black Senior Scientist Advanced Analytics Directorate Northrop Grumman Information Systems
________________________________ From: sqlite-users-boun...@sqlite.org on behalf of Tod Wulff Sent: Wed 12/29/2010 2:53 AM To: 'General Discussion of SQLite Database' Subject: EXTERNAL:[sqlite] FTS4 snippets contains unintended content? Good day. Anyone seeing additional content returned with the snippet text when using the OR (or AND?) MATCH Syntax - i.e. the field contents of the field immediately prior to the snippet(blah) clause? SELECT Target_Name, Target_Content, Target_Description, Target_Link, Parent_Short, Parent_Name, Parent_Link, API_Version, rowid, snippet(RIM_API_FTS_DB, ' ', ' ', '...', -3, -10) FROM RIM_API_FTS_DB WHERE RIM_API_FTS_DB MATCH 'bug report API_Version:374 OR API_Version:UAR' ORDER BY rank(matchinfo(RIM_API_FTS_DB), 50, 10, 25, 15, 0, 0, 0, 0, 0 ) DESC LIMIT 10 OFFSET 0; In the snippet col in each result row, I get the ...[snippet text]... XXX ß Where XXX is the content of the field called out in the MATCH clause. It only shows up when I use the OR MATCH Syntax. I haven't tested with AND yet. [03:41] <Schema> 1: [3.7.4] Release History Of SQLite ( http://j.mp/fHI3HG ) ...generator bug introduced in version 3.6.14 . This bug ...status() interface, in order to report out the amount of... 374 [03:41] <Schema> 2: [3.7.4] SQLite Older News ( http://j.mp/fX8ErX ) ...single notable bug was fixed (ticket #3929). This bug cause...still be considered alpha. Please report any problems. The file... 374 [03:41] <Schema> 3: [3.7.4] How SQLite Is Tested ( http://j.mp/gdqXN1 ) ...Whenever a bug is reported against SQLite, that bug is...0 (all statistics in the report are against that release... 374 [03:41] <Schema> 4: [3.7.4] About SQLite ( http://j.mp/gw9S60 ) ...Interface Spec Development Timeline Report a Bug Wiki SQLite is... 374 [03:41] <Schema> 5: [UAR] SQLite Changes From Version 3.5.9 To 3.6.0 ( http://j.mp/f6M2jc ) ...allows the xAccess() method to report failures. In association with...IN operators is technically a bug fix, not a design... UAR Please chime in if you have seen this. Thanks, in advance. -t _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
