#207: Recurring events do not appear to extend beyond November 2008
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: Defect | Status: new
Priority: 1: Blocker | Milestone: 2.x
Component: Calendar Server | Version:
Severity: Serious | Resolution:
Keywords: |
------------------------------------+---------------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:4 [EMAIL PROTECTED]:
> The index is supposed to indicate how far out expansion has happened for
each event, and if a query against the index goes beyond that time, the
expansion should be brought out farther, up to a defined limit.
Yes but that indication is stored in the RESOURCE table in RECURRANCE_MAX
and unless I'm sorely mistaken a simple grep will show that RECURRANCE_MAX
is used no where in the 1.2 code except in "create table" statements and
in the "insert into" statement which first inserts the event into the
RESOURCE table. (index.py).
No where is the value brought out farther.
I'm sad to see this bumped to milestone 2.x. I would suspect this to be a
serious blocker for any practical use. No events of the "same time, next
year" kind can be used in the calendar. Anniversaries and every other
event more than 356 days into the future will also disappear.
--
Ticket URL: <http://trac.calendarserver.org/ticket/207#comment:5>
CalendarServer </>
HTTP/WebDAV/CalDAV Server
_______________________________________________
calendarserver-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-dev
