Add support for a exceptionoriginaldate field.
authorMichael J. Rubinsky <mrubinsk@horde.org>
Sun, 4 Apr 2010 03:43:52 +0000 (23:43 -0400)
committerMichael J. Rubinsky <mrubinsk@horde.org>
Sun, 4 Apr 2010 03:43:52 +0000 (23:43 -0400)
commit3b030fc7ccb37115875de24d366fa12579d76760
treed2fb8f494fb5d9025aeb46dd1fa4e52a1dfdebc2
parent7abf2ec72c3c1a93741e0c288062ab47e398ad79
Add support for a exceptionoriginaldate field.

This field tracks the start date of the instance of the recurring event that
an exception is for.  This is needed for sync clients to be able to know
if a specific recurring event instance has been deleted. Since if the exception
starts on a different date (and not just a different time), it's impossible to
match up the events representing exceptions with the list of exceptions in the
Kronolith_Event object.

Now that we have this information, we can get the list of events that represent
exceptions (i.e. event_baseid == the uid of the original recurring event) and
match them up with the list of exceptions in the $event->exceptions. Any left
over dates in $event->exceptions represent instances of the recurring event
that have been deleted.
12 files changed:
kronolith/edit.php
kronolith/lib/Driver/Sql.php
kronolith/lib/Event/Sql.php
kronolith/scripts/sql/kronolith.mssql.sql
kronolith/scripts/sql/kronolith.mysql.sql
kronolith/scripts/sql/kronolith.oci8.sql
kronolith/scripts/sql/kronolith.pgsql.sql
kronolith/scripts/sql/kronolith.sql
kronolith/scripts/sql/kronolith.xml
kronolith/scripts/upgrades/2010-04-03_add_exceptionoriginaldate.oci8.sql [new file with mode: 0644]
kronolith/scripts/upgrades/2010-04-03_add_exceptionoriginaldate.pgsql.sql [new file with mode: 0644]
kronolith/scripts/upgrades/2010-04-03_add_exceptionoriginaldate.sql [new file with mode: 0644]