couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Young (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-576) Require current update_seq when deleting a database for extra safety.
Date Fri, 28 Sep 2012 14:31:07 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465640#comment-13465640
] 

Benjamin Young commented on COUCHDB-576:
----------------------------------------

Use of seq is perhaps silly, but database should really be at least as hard to delete as documents
are. Right now it's *much* simpler to annihilate loads of work than it is to destroy a single
document.

Maybe a random UUID stored per DB used only for delete?
                
> 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

Mime
View raw message