[
https://issues.apache.org/jira/browse/COUCHDB-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466810#comment-13466810
]
Dave Cottlehuber commented on COUCHDB-576:
------------------------------------------
OK, I'm +1 for addressing that. Thanks Bob for the clarification.
update-seq looks good to me, so long as this doesn't introduce a race condition
for frequently written DBs.
I have an aversion to UUIDs inside the DB, it's not a nice thing if ops people
restore a .couch to extract some docs from it & then things go haywire as a
more recent version of the DB with the same UUID exists. Some other suggestions
in COUCHDB-782 of generating it dynamically on open is interesting, but I am
not sure that would work for people with proxies in front of replicated couch
clusters.
> Require current update_seq when deleting a database for extra safety.
> ---------------------------------------------------------------------
>
> Key: COUCHDB-576
> URL: https://issues.apache.org/jira/browse/COUCHDB-576
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Reporter: Robert Newson
> Attachments: delete-db-safety-with-tests.patch
>
>
> Require the current update_seq before deleting a database to prevent
> accidental deletion.
> DELETE /db2?seq=12
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
