Hi devs,
found another bug:
1.create event series at arbitrary time and repeat e.g. yearly
2.create exception at e.g. second recurrence, now my table “egw_cal” looks as it should be:
±-------±----------------±-------------------------+
| cal_id | recur_exception | from_unixtime(cal_start) |
±-------±----------------±-------------------------+
| 118271 | 0 | 2013-03-18 16:00:00 |
| 118271 | 1 | 2014-03-18 16:00:00 |
| 118271 | 0 | 2015-03-18 16:00:00 |
±-------±----------------±-------------------------+
-
move master event to another time, now same event is missing the second recurrence in “egw_cal”. User still thinks everything is fine even if db is missing the exception.
±-------±----------------±-------------------------+
| cal_id | recur_exception | from_unixtime(cal_start) |
±-------±----------------±-------------------------+
| 118271 | 0 | 2013-03-18 12:00:00 |
| 118271 | 0 | 2015-03-18 12:00:00 |
±-------±----------------±-------------------------+
-
now move master event again to another start time, application does not recognize that there was an exception and recalculates recurrences without any exception; now the user sees a duplicate at second recurrence (the master’s recurrence AND the exception created before).
±-------±----------------±-------------------------+
| cal_id | recur_exception | from_unixtime(cal_start) |
±-------±----------------±-------------------------+
| 118271 | 0 | 2013-03-18 13:00:00 |
| 118271 | 0 | 2014-03-18 13:00:00 |
| 118271 | 0 | 2015-03-18 13:00:00 |
±-------±----------------±-------------------------+
Greetings
Christian
