[
https://issues.apache.org/jira/browse/COUCHDB-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087485#comment-13087485
]
Jason Smith commented on COUCHDB-1252:
--------------------------------------
I propose this issue be closed as NOFIX (or whatever it's called). Allowing
include_deleted would confuse the concept of "deleted" in the way that calling
them "revisions" implies that CouchDB revisions are great for a wiki.
James, your requirements are brilliant. That sounds like a great app. But IMO
if you need data to remain indefinitely (for audit), then you should not be
deleting documents and then exploiting the fact that CouchDB keeps deleted
documents for revision tracking. In your application, "deleted" means
"invisible to users but the auditors still want to know about it" so that is an
application-level detail. That is exactly what views are for.
For an application, _deleted means it's dead. Advanced tools like the
replicator must follow the doc into the afterlife but that's not an
application's concern.
> A way to have views return _deleted documents
> ---------------------------------------------
>
> Key: COUCHDB-1252
> URL: https://issues.apache.org/jira/browse/COUCHDB-1252
> Project: CouchDB
> Issue Type: New Feature
> Components: JavaScript View Server
> Affects Versions: 1.1, 1.0.3
> Reporter: James Howe
>
> Given that documents can be 'soft' deleted / deleted with auditing data by
> updating the document to include the _deleted property, it would be
> incredibly useful if there were a way to access these documents in a map
> function. Otherwise it is very difficult to find the auditing data - even
> more so if the original ids are unknown.
> I was thinking along the lines of a view query parameter 'include_deleted',
> but don't really mind how this is implemented, as long as it is there.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
