and indeed it does have three attachments with the same name.  I'm not sure what the next step is here.  We certainly don't want replication to break, but this seems like such an edge case that I'm not sure it's worth putting in special code in the replicator to deal with it. 

Damien, the check_dup_atts code is your stuff, right?  Do you know how Benoit could've ended up with 3 identically-named attachments in the past? 

Adam Kocoloski
added a comment - 14/Aug/09 04:48 So we identified the document that has duplicate attachments as
http://benoitc.im/b/7cb06e5de28327c7fc81c7028bece5a3
and indeed it does have three attachments with the same name.  I'm not sure what the next step is here.  We certainly don't want replication to break, but this seems like such an edge case that I'm not sure it's worth putting in special code in the replicator to deal with it. 
Damien, the check_dup_atts code is your stuff, right?  Do you know how Benoit could've ended up with 3 identically-named attachments in the past?