And one more general point. For me, this proposal predates Mango by a couple of years, I only now got around to writing it up.
When I talked about this potential feature internally at work, we came to the conclusion that it might be less confusing to use Mango index definitions here, instead of JSON Pointer. The benefit of JSON Pointer fitting natively into URLs are nice, but not necessarily important enough to introduce two different ways for specifying how to specify fields inside a document. As a refresher, here’s [how Mango does it](http://docs.couchdb.org/en/stable/api/database/find.html#db-index): ``` { "index": { "fields": ["foo.bar.baz.3"] }, "name" : "foo-index", "type" : "json" } ``` this would index `d` this doc: ``` { "foo": { "bar": { "baz": ["a", "b", "c","d","e","f"] } } } ``` So effectively, Mango syntax is just like JSON Pointer, expect every `/` is a `.`. I think this would make for a more coherent proposal. [ Full content available at: https://github.com/apache/couchdb/issues/1559 ] This message was relayed via gitbox.apache.org for [email protected]
