[
https://issues.apache.org/jira/browse/COUCHDB-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson resolved COUCHDB-196.
------------------------------------
Resolution: Fixed
Resolved by r733116.
Docids do not use the same collation as string view keys, so the _all_docs view
was getting endkeys wrong. Fixed so that all_doc uses the same comparison as
doc insertion to handle endkeys.
> Bug in _all_docs: extra incorrect row returned when ?key= is specified
> ----------------------------------------------------------------------
>
> Key: COUCHDB-196
> URL: https://issues.apache.org/jira/browse/COUCHDB-196
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Jason Davies
> Attachments: collation_ids.diff, collation_test.2.diff,
> collation_test.diff, couch_db_updater.diff, docid_collation.diff, view_coll.js
>
>
> I first noticed this when attempting to reverse the order of docs displayed
> in Futon, when listing the design docs. When the order is reversed,
> non-design docs are displayed.
> After digging deeper I discovered that querying _all_docs with key="Z" can
> potentially return two rows, with keys "Z" and "a".
> I will attach a test case to reproduce this. My locale is set to
> en_GB.UTF-8, which could be related to this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
