[Cosmo-dev] another issue with items in multiple collections

[Randy Letness]

I seem to be using this subject a lot.

Bug 10212 describes the issue:  
https://bugzilla.osafoundation.org/show_bug.cgi?id=10212

To summarize:

1. create collection 1, add item A
2. create collection 2, add item A
3. publish collection 1
4. publish collection 2
5. remove item A from collection 1
6. sync collection 1 --> item A re-appears

This is occurring because the sync operation involves getting all the 
updated records since the last sync (the publish in this case).  When 
collection 2 was published, it included the recordset for item A so the 
server assumes A has changed.  When collection 1 is synced, these 
changes are sent back before the client sends the deletions and these 
changes override the deletions and the recordset deletions never get 
sent to the server.

I think this is just Chandler's policy, that is server changes always 
override local changes.  It would be nice if the client informed the 
user that the item has been updated and gave them a choice of keeping 
the item or removing it.  The same thing would happen if a different 
Chandler client updated item A before the other client deleted and then 
synced.  I'm not sure there is a lot the server can do about this.  
Thoughts?

This would work fine if the above steps were changed to:

1. create collection 1, add item A
2. create collection 2, add item A
3. publish collection 1
4. publish collection 2
5. sync collection 1
6. remove item A from collection 1
7. sync collection 1

-Randy