Bug #2337
closed
Confirmed, "is not" returns the same results as "is".
Reviewing further if the "Between" date is specified and not the "and" date then it'll find everyone with a date GREATER than specified. If the "and" date is specified and NOT the "Between" date then it'll find everyone with a date LESS than specified. This can be reversed with an IF statement to change the search operator based off search mode, which seams best approach (making "Between" the less than and "and" the greater than).
- Status changed from New to Feedback
- Assignee changed from krileon to beat
Seams cbSqlQueryPart needs to be expanded to handle ranges. Example query below with current usage of isnot.
WHERE ((u.`lastvisitDate` >= '2011-01-26')
AND (u.`lastvisitDate` <= '2011-01-28'))
If expanded to handle ranges would be as follows.
WHERE ((u.`lastvisitDate` NOT BETWEEN '2011-01-26' AND '2011-01-28'))
- Status changed from Feedback to Assigned
- Assignee changed from beat to krileon
Appears can be resolved using OR instead of AND in those scenarios, which API certainly supports.
- File 2337.patch 2337.patch added
- Status changed from Assigned to Resolved
- Assignee changed from krileon to beat
- % Done changed from 0 to 100
Completely rewrote the code responsible for search query criteria. Using addChildren method when necessary was able to provide an AND/OR scenario.
- Target version set to CB 1.7
- Estimated time set to 3:00 h
- Status changed from Resolved to Closed
Fixed in r1487 by implementing the proposed patch. Thank you Kyle.
Also available in: Atom
PDF