Closed giftig closed 5 years ago
I guess this matches the rest of the API design since to read, modify, and update a document you'd need to pass around the full CouchDoc
instance or you'd lose kind
details mapped to types. The API feels a little invasive in that you potentially have to expose multiple layers of application code to the database's types, though, whereas just an id and rev is (relatively) generic and portable.
This seems overkill, as I know the id and rev of the document I want to delete but don't have a full
CouchDoc
reference as I discarded it to avoid leaking db layer details into my code.id
andrev
is all that's required, and indeed your implemention is:so any other details shouldn't be required. As a workaround I'm simply doing this: