[Cosmo-dev] detaching item occurrences

[Brian Moseley]

On 8/10/07, Randy Letness <randy at osafoundation.org> wrote:

> So basically the client is creating a new recurring event based on the
> existing event and any changes.  This means the client is responsible
> for creating the complete recordset for the new recurring event.  By
> using this special projection the server knows to modify the existing
> recurring event (breaking the series at that point) and moving any
> relevant modifications to the new recurring event.

ok, that explains why my detached item wasn't showing multiple
occurrences - i didn't include a recurrence rule in the detached
record set.

still doesn't explain why the account browser was using the old uid
for the detached item instead of its new uid... we'll need to keep
looking into that one.