This is not a server issue, the implementation of date range domains is
correct, you are just *meaning* something about the combination of your 2 date
criterions acting as a range that the system cannot understand. You really mean
these 2 dates as a range, but there is no way to express that simply.
We do not have any range operators at the moment, but you could instead use a
custom search() method, as suggested by Anup.
Or if you simply want to implement this in search views, you could use
smarter domains using the filter_domain attribute on the date fields of
your search view.
** Changed in: openobject-server
Status: Triaged => Invalid
--
Date range search incomplete
https://bugs.launchpad.net/bugs/578662
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
Status in OpenObject Server: Invalid
Bug description:
Searching objects by specifying a date range does not always get all the
objects that should match.
Let's say there is an event starting on 2010-05-07 and ending on 2010-07-01. If
I search all the events for week 19: 2010-05-10 to 2010-05-16, I should get
this event because it is occurring that week too. But in fact it does not
appear in the list because the search domain used is:
[('date_begin', '>=', '2010-05-10'), ('date_begin', '<=', '2010-05-16')]
Object being tested: 'event.event'
Version: 5.0
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
