| Summary | Day View: request on three days ? |
| Queue | Kronolith |
| Queue Version | 2.3.4 |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | patrick.abiven (at) apitech (dot) fr |
| Created | 05/10/2010 (5542 days ago) |
| Due | |
| Updated | 05/13/2010 (5539 days ago) |
| Assigned | |
| Resolved | 05/13/2010 (5539 days ago) |
| Milestone | 2.3.5 |
| Patch | No |
Fix setting end date (
Bug #9011).http://cvs.horde.org/diff.php/kronolith/lib/Driver/sql.php?rt=horde&r1=1.136.2.47&r2=1.136.2.48&ty=u
State ⇒ Resolved
Milestone ⇒ 2.3.5
Don't retrieve events two days into the future (
Bug #9011).http://cvs.horde.org/diff.php/kronolith/lib/Driver/sql.php?rt=horde&r1=1.136.2.46&r2=1.136.2.47&ty=u
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Day View: request on three days ?
Type ⇒ Enhancement
State ⇒ New
It seems that when using a Day View (on day D), the sql request is
querying events from D to D + 2 days.
Driver/sql.php: listEvents(): $endInterval = nextDay ($endDate)
Driver/sql.php: listEventsConditional(): $endInterval = $endInterval + 1.
Can we reduce the number of days searched ?
Best regards
Patrick