Every now and then, there are requests to allow editing events that were created as "repeating events" in one go. Right now, you can create identical events all at once, but after that you have to edit or delete them one by one.
Therefore I propose doing the following, and hope that it's not too late:
- Add a column "int repeatid default 0" to mdl_event.
- When creating events, if they are not created as part of a repeat, keep repeatid = 0. Otherwise, query the database for the next unused value of repeatid and set that to all created events.
- Now it's trivial to know if an event was created as part of a repeat, and to also find all other events in that repeat group (only they share the same repeatid).
- In the "delete event" confirmation screen, if an event is part of a repeat, give the option to "delete all".
It's not difficult to think of other uses of repeatid: when moving an event in time, move all other repeat instances by the same amount of time; when editing the event title, update all repeat instances with the new title; same for description; same for changing the duration.
All this won't take much time to do. Votes? Vetoes?
, if not, an early addition to 1.6. 