couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (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 18:25:07 GMT

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

Paul Joseph Davis commented on COUCHDB-576:
-------------------------------------------

Using the update_seq or a UUID is probably the best way forward. We've already talked about
adding a UUID to each database anyway so that seems probably the best route.

The ?type approach just seems awkward and really not much of a help if you can still accidentally
delete things when you're in a hurry and don't bother specifying a ?type value.
                
> 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