>That's not in line with current API semantics:
>Query won't show "empty aka deleted" documents,
A Document that has 'contents' from the underlying data repository that are represented by an empty JSON string ("{}") and one that is completely empty ("") are not (supposed to be) the same thing. The former is intended to create a JSON object, the latter is not. The former is still (supposed to be) a document, the latter is supposed to be a 'deleted' document (aka tombstone).
Tombstone is actually the less misleading term, because no document is every really deleted. In the reference implementation only its content property is deleted. A tombstone document can still be retrieved from the database, but when trying to request its contents the user / developer will get an error that 'contents' does not exist as part of the obkext. (Or something to that effect).
>That's not in line with current API semantics:
>Query won't show "empty aka deleted" documents,
A Document that has 'contents' from the underlying data repository that are represented by an empty JSON string ("{}") and one that is completely empty ("") are not (supposed to be) the same thing. The former is intended to create a JSON object, the latter is not. The former is still (supposed to be) a document, the latter is supposed to be a 'deleted' document (aka tombstone).
Tombstone is actually the less misleading term, because no document is every really deleted. In the reference implementation only its content property is deleted. A tombstone document can still be retrieved from the database, but when trying to request its contents the user / developer will get an error that 'contents' does not exist as part of the obkext. (Or something to that effect).