[
https://issues.apache.org/jira/browse/COUCHDB-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563018#comment-14563018
]
ASF GitHub Bot commented on COUCHDB-2657:
-----------------------------------------
GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/447
remove hard reset of couchdb's master
COUCHDB-2657
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-fauxton
remove-hard-reset
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fauxton/pull/447.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 #447
----
commit 4a3925532cff3b63801e911c28f042fad6017fc4
Author: Robert Kowalski <[email protected]>
Date: 2015-05-28T14:51:12Z
remove hard reset of couchdb's master
COUCHDB-2657
----
> if _metadata is there, creating a db does not work
> --------------------------------------------------
>
> Key: COUCHDB-2657
> URL: https://issues.apache.org/jira/browse/COUCHDB-2657
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: BigCouch, Database Core
> Reporter: Robert Kowalski
> Priority: Blocker
>
> with the new _setup_cluster endpoint a _metadata db is created.
> when it exists, and we create a db, read it _all_doc immediatly [1] (Fauxton
> does that) we get:
> `document update conflict`
> [1]
> http://localhost:8000/sdfsdtest/_all_docs?startkey=%22_design%2F%22&endkey=%22_design0%22&include_docs=true&limit=501
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
