> On Aug 3, 2015, at 3:06 PM, Todd Freese <[email protected]> wrote:
>
> http://...:4985/mydb/_design/scenes_for_job/_view/scenes_for_job?endkey=["FEB04B15-C3E7-4885-9275-395C350F1F00","\uefff";]
>
> <http://approvalstest.filmworkers.com:4985/shotbotdb/_design/scenes_for_job/_view/scenes_for_job?endkey=%5B%22FEB04B15-C3E7-4885-9275-395C350F1F00%22,%22%5Cuefff%22%5D>&descending=false&stale=false
It would be better to use {} as a placeholder instead of “\uefff”. I don’t
think it makes a difference in this case, but {} is the usual idiom for
“something larger than any possible key”. The huge-Unicode-character is sort of
a kludge that’s appended to a string to get a prefix match.
> My data returning from this has the same doc.job_id for all docs and
> different doc.sceneNumber for each doc. I would like an ascending sort on
> sceneNumber.
It should be returning rows for all docs where the job_id is ≤ “FEB04…”.
What order do the scene numbers actually appear in? (And did you make sure that
sceneNumber is a number not a string?)
—Jens
--
You received this message because you are subscribed to the Google Groups
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/mobile-couchbase/174EF5CD-2092-4A54-BCC0-73B07FE1CC5B%40mooseyard.com.
For more options, visit https://groups.google.com/d/optout.
