couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Chesneau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-576) Require current update_seq when deleting a database for extra safety.
Date Sat, 29 Sep 2012 12:24:08 GMT

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

Benoit Chesneau commented on COUCHDB-576:
-----------------------------------------

how will it make it difficult? Some are already forcing delet by fetching latest rev each
time .... Imo forcing the need of an admin could do the trick. Right now we don't force the
creation of an admin on startup but maybe we should like other dbs. Since only admins can
delete a db...
                
> 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