couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-576) Require current update_seq when deleting a database for extra safety.
Date Mon, 01 Oct 2012 12:41:07 GMT


Dave Cottlehuber commented on COUCHDB-576:

Futon & API clients will simply wrap this functionality in anyway so I think it's only
people using cURL, right? So I'm undecided on this. I agree with the intent, I've done this
myself from time to time. But what type of DELETE are we intending to prevent?

- Honey I deleted the wrong DB?
- Honey I didn't have a backup?

- futon will presumably help out and provide the seq or whatever anyway for non-thinking admins
- API clients will get updated to handle this transparently

I think requiring admin is not a bad idea, but I suspect we're only protecting a relatively
small number of developers. Is there an angle in Bigcouch/cloudant that makes this much more
important, aside from sheer size of DBs?

What does DROP TABLE or whatever require in an RDBMS? or "zfs destroy" etc? Any bulk store
has this risk/feature.

> Require current update_seq when deleting a database for extra safety.
> ---------------------------------------------------------------------
>                 Key: COUCHDB-576
>                 URL:
>             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:

View raw message