我正在构建一个需要支持重复事件的组日历应用程序，但我提出的处理这些事件的所有解决方案似乎都很简单。我可以限制一个人可以看多远的未来，然后一次性生成所有事件。或者，我可以将事件存储为重复的，并在日历上动态显示它们，但如果有人想更改事件的特定实例的细节，则必须将它们转换为正常事件。
我相信有更好的办法，但我还没找到。对重复发生的事件建模的最佳方法是什么?在这种方法中，您可以更改或删除特定事件实例的细节?
(我使用Ruby，但请不要让这限制了你的回答。如果有ruby特定的库或其他东西，那么最好知道。)
当前回答
I would use a 'link' concept for all future recurring events. They are dynamically displayed in the calendar and link back to a single reference object. When events have taken place the link is broken and the event becomes a standalone instance. If you attempt to edit a recurring event then prompt to change all future items (i.e. change single linked reference) or change just that instance (in which case convert this to a standalone instance and then make change). The latter cased is slightly problematic as you need to keep track in your recurring list of all future events that were converted to single instance. But, this is entirely do-able.
因此，在本质上，有两类事件-单个实例和重复事件。
其他回答
如果你有一个没有结束日期的重复约会怎么办?虽然空间很便宜，但你没有无限的空间，所以解决方案2在那里是行不通的……
我建议，“没有结束日期”可以解决到本世纪末的结束日期。即使是日常活动，场地数量也很便宜。
From these answers, I've sort of sifted out a solution. I really like the idea of the link concept. Recurring events could be a linked list, with the tail knowing its recurrence rule. Changing one event would then be easy, because the links stay in place, and deleting an event is easy as well - you just unlink an event, delete it, and re-link the event before and after it. You still have to query recurring events every time someone looks at a new time period never been looked at before on the calendar, but otherwise this is pretty clean.
Keep track of a recurrence rule (probably based on iCalendar, per @Kris K.). This will include a pattern and a range (Every third Tuesday, for 10 occurrences). For when you want to edit/delete a specific occurrence, keep track of exception dates for the above recurrence rule (dates where the event doesn't occur as the rule specifies). If you deleted, that's all you need, if you edited, create another event, and give it a parent ID set to the main event. You can choose whether to include all of the main event's information in this record, or if it only holds the changes and inherits everything that doesn't change.
请注意，如果允许不终止的递归规则，则必须考虑如何显示现在无限多的信息。
希望有帮助!
将事件存储为重复事件并动态地显示它们，但是允许重复事件包含特定事件的列表，这些事件可以覆盖特定日期的默认信息。
当您查询重复发生的事件时，它可以检查当天的特定覆盖。
如果用户进行了更改，那么您可以询问他是希望更新所有实例(默认详细信息)还是仅更新当天(创建一个新的特定事件并将其添加到列表中)。
如果用户要求删除此事件的所有递归，您还可以获得详细信息列表，并可以轻松删除它们。
唯一有问题的情况是用户想要更新这个事件和所有未来的事件。在这种情况下，你必须把重复发生的事件分成两部分。此时，您可能需要考虑以某种方式链接重复发生的事件，以便将它们全部删除。
对于准备支付一些授权费用的。net程序员，您可能会找到Aspose。网络很有用…它包括一个iCalendar兼容库，用于重复约会。
