Github user davisp commented on the pull request:

    https://github.com/apache/couchdb-fabric/pull/6#issuecomment-66816904
  
    Yeah, the is_replicator_db and is_users_db should probably be in 
couch_replicator and couch_users_db but I figured we can clean that up later if 
need be.
    
    As to idempotency, I think that should actually be a requirement and the 
users db is just being naughty here. We've long told everyone that 
validate_doc_update can't edit documents due to replication causing conflicts 
and this is basically sitting at the same place in a doc's lifecycle.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to