-
Notifications
You must be signed in to change notification settings - Fork 31
FindManyAsync returns deleted documents, but not sure how to identify them? #154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, that's a tricky one. Is that correct that the DB returns deleted documents in the first place? |
The FindManyAsync method, uses the _bulk_get CouchDB endpoint, if I use Thunder Client/Postman and pass a deleted document id, such as:
I get the following result:
|
I trust you, I am asking because it's not documented on their end |
I'm guessing it's by design, but poorly documented, there's some information on the _delete flag here: https://docs.couchdb.org/en/stable/api/document/common.html#get--db-docid The most convincing bit would probably be the first link where it documents the GET /{db}/{docid} endpoint and describes the flag as _deleted (boolean) – Deletion flag. Available if document was removed. However, further down the document the following section seem to suggest you need to supply a rev to retrieve the deleted document (I've not tried this, so I can't confirm, but if that is the case then maybe the _bulk_get function is suppose to work the same way and there is a genuine bug with it?): https://docs.couchdb.org/en/stable/api/document/common.html#retrieving-deleted-documents |
Hi, I've added the following to properties to my document as a workaround until this gets fixed:
|
Hi, I think we can add a parameter to filter out delete documents |
It took a lot, but I added the property :) |
FindManyAsync seems to return deleted documents, Is there currently a way to identify if the document is deleted or not?
If not would it be possible to expose _deleted=true on the CouchDocument for example.
Thanks
The text was updated successfully, but these errors were encountered: