ricellis commented on issue #2666: soft-deletion for database URL: https://github.com/apache/couchdb/pull/2666#issuecomment-604325420 > Obviously we don't have an `_undelete` database but it is technically mixing that API endpoint into the valid range of database names. Agree that is probably better avoided. I was thinking that maybe we could keep the functionality in the `_deleted_dbs` namespace by `POST /_deleted_dbs` with something like this: ```json { "undelete": { "source": "source_database_name", "source_timestamp": "2020-03-24T12:00:00", "target": "target_database_name" } } ``` but ultimately I think that probably ends up more opaque than just using differently named endpoint `POST /_undelete_db` so I'm OK with `_undelete_db`. @mikerhodes as the initial proposer of the `_deleted_dbs/_restore` pattern are you OK with `POST /_undelete_db`? Unrelated to the endpoint name the example shows no TZ data in the ISO-8601 timestamp, is that an accurate representation of the output/input we're expecting?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
