Yes, that’s the defined behavior, and it will persist in 2.x. You need to take this into account when you write your map function; e.g. if you `emit([“keyB”, “keyA”], “value);` and then query for [“keyA”,”keyB”] you will not get a match. Regards,
Adam > On Aug 22, 2015, at 8:02 AM, Stefan Klein <[email protected]> wrote: > > Hi CouchDB users, > > when I query a view with keys=["keyA", "keyB"] the returnd rows also > list the matches for "keyA" first, then matches for "keyB". If i query > with ["keyB","keyA"] the results reflects this and lists matches for > "keyB" first. > This is for my local couchdb 1.6.1. > Is this behaviour guaranteed for 1.6.1? > Will it also be guaranteed for 2.x? > Or does couchdb just happen to behave so on my installation? > > thanks, > Stefan >
