On Thu, 2012-02-09 at 07:52 +0100, [email protected] wrote: > On Wed, Feb 08, 2012 at 20:51:41 +0100, Patrick Ohly wrote: > > In such a combination it is possible that the server ends up storing two > > independent items with the same UID, because the file backend is > > oblivious of the iCalendar 2.0 UID/RECURRENCE-ID semantic. When that > > happens, the server asks the client to store an item that the client > > already has, which the client can detect based on the UID/RECURRENCE-ID. > > The client then refuses to add that item again with the 409 status to > > the engine. > > So I can fix this by removing duplicates manually on the server side > file storage, right?
That, or doing a "refresh-from-client". The data on the client side should be okay. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
