Opened 16 years ago
Closed 16 years ago
#318 closed defect (incomplete)
omega datestart/datestop returns incorrect results
| Reported by: | stvs | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Omega | Version: | 1.0.2 |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
Description
There is something wrong in Omega's datestart/datestop handling:
If I supply the following arguments:
HITSPERPAGE=20&MINHITS=50&START=20081216&END=20081223
Omega says the TOTAL amount of matches is 20. Which isn't true.
If I increase HITSPERPAGE to 24 (for the same query):
HITSPERPAGE=24&MINHITS=50&START=20081216&END=20081223
Omega returns 24 as total amount of matches.
I've been through changelogs to check wether this has been fixed in newer versions but haven't be able to find a solution. If you need more information, please let me know!
Change History (3)
comment:1 by , 16 years ago
| Severity: | major → normal |
|---|
comment:3 by , 16 years ago
| Resolution: | → incomplete |
|---|---|
| Status: | new → closed |
There's not a lot we can do based on the information supplied so far, and it's quite likely this was fixed by "checkatleast" fixes made since 1.0.2.
A "ping" 6 weeks ago got no response, so closing as "incomplete".
If you are able to reproduce this in a more recent version and want to supply more information, feel free to reopen this ticket.
I think we really need to find out if this bug is present in the latest release - there are two fixes related to check_at_least handling in xapian-core 1.0.3 for starters (which is the feature MINHITS makes use of).
So can you either install the latest release of xapian-core and omega and retest, or provide a way we can reproduce your test setup (if the database is small, you can just tar it up and attach it to this ticket).
What platform is this on?