[
https://issues.apache.org/jira/browse/COUCHDB-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243604#comment-14243604
]
ASF GitHub Bot commented on COUCHDB-2510:
-----------------------------------------
GitHub user davisp opened a pull request:
https://github.com/apache/couchdb-fabric/pull/6
Add system db handlers to fabric_doc_update
This hard codes the before_doc_write functions for replicator and user
databases like they are in couch_server. This is mostly motivated by the
fact that couch_users_db:before_doc_update/1 adds random salt values to
user documents when a password is changed. The replicator databases are
included at this level for consistency with couch_server.
COUCHDB-2510
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/couchdb-fabric
2510-add-system-db-handlers
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fabric/pull/6.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6
----
commit 4e0e81fd9d668bf4d532864b9cab3ad2d7653d50
Author: Paul J. Davis <[email protected]>
Date: 2014-12-12T02:13:57Z
Add system db handlers to fabric_doc_update
This hard codes the before_doc_write functions for replicator and user
databases like they are in couch_server. This is mostly motivated by the
fact that couch_users_db:before_doc_update/1 adds random salt values to
user documents when a password is changed. The replicator databases are
included at this level for consistency with couch_server.
COUCHDB-2510
----
> Apply system db before_doc_update functions in fabric
> -----------------------------------------------------
>
> Key: COUCHDB-2510
> URL: https://issues.apache.org/jira/browse/COUCHDB-2510
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Database Core
> Reporter: Paul Joseph Davis
> Assignee: Paul Joseph Davis
>
> This is mostly for the users db because it makes random changes to the user
> documents before writing them to disk. In a cluster this is a guarantee that
> we'll end up with three conflicts each time a user updates their password.
> This just hardcodes the two system databases into fabric's doc update handler
> the same as they're hard coded in couch_server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
