Ticket #611 (defect)
Opened 3 years ago
Date range query incorrect?
Status: new
| Reported by: | douglm | Assigned to: | douglm |
|---|---|---|---|
| Priority: | major | Milestone: | Bedework 3.7 |
| Component: | unclassified | Version: | |
| Keywords: | Cc: | ||
I believe there's a problem to deal with here (2 actually)
bweventann0_.bw_start_floating='T'
and bweventann0_.start_date<'20100822T040000Z'
and (
bweventann0_.end_date>'20100815T040000Z'
or bweventann0_.start_date=bweventann0_.end_date
and bweventann0_.end_date>='20100815'
)
or (
bweventann0_.bw_start_floating is null
)
and bweventann0_.start_date<'20100822T040000Z'
and (
bweventann0_.end_date>'20100815T040000Z'
or bweventann0_.start_date=bweventann0_.end_date
and bweventann0_.end_date>='20100815'
)
is what's generated for the override fetch (it's the same for all date range fetches).
1. There's no allowance for date type starts 2. There's no allowance for the value in the entries being null. Tasks don't need an end. Do I add an end value or should this allow for it?
