diff options
| author | Sascha Silbe <silbe@activitycentral.com> | 2011-03-04 14:02:03 (GMT) |
|---|---|---|
| committer | Sascha Silbe <silbe@activitycentral.com> | 2011-03-04 14:02:03 (GMT) |
| commit | 40dc8979c7b22fb23b8cdf93f3fd810a3b46269d (patch) | |
| tree | e7bc6e08393cd60c341e023032f5edc272eab20d | |
| parent | 5716859ce89e9e164cc720aaef4a2ec75a36b8c0 (diff) | |
| parent | 62e3f3da8b4e8d60a3396b2056d1d58f8719fb43 (diff) | |
Merge remote branch 'refs/remotes/origin/t/timestamp-range-query-fix' into HEAD
* refs/remotes/origin/t/timestamp-range-query-fix:
fix range query for timestamp to do numerical comparison instead of lexical (#1342)
| -rw-r--r-- | .topdeps | 3 | ||||
| -rw-r--r-- | .topmsg | 14 |
2 files changed, 10 insertions, 7 deletions
@@ -1,2 +1 @@ -upstream/master -t/testsuite +t/query-typed-props @@ -1,10 +1,14 @@ From: Sascha Silbe <sascha@silbe.org> -Subject: [PATCH] add and use type information for "known" properties (#1437) +Subject: [PATCH] fix range query for timestamp to do numerical comparison instead of lexical (#1342) -Bug #1342 has shown that it's necessary to know (and convert/check) the type -of known properties (as we need to use xapian.sortable_serialise() on numeric -types). This patch does that (but doesn't fix #1342 yet, that will be done on -top of it). +With the current code, anything Xapian value-stored is converted to a string +before querying, so numeric types end up as decimal strings. This won't work as +expected because Xapian does lexical comparison. We need to use +xapian.sortable_serialise() on numeric values to convert them to an (internal) +format that will result in "numerical" comparison. +Changes index content format, so needs an index rebuild. + +Prerequisite: #1437 Signed-off-by: Sascha Silbe <sascha@silbe.org> |