[
https://issues.apache.org/jira/browse/COUCHDB-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Davies updated COUCHDB-196:
---------------------------------
Description:
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.
was:
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 is probably related to this problem.
Summary: Bug in _all_docs: extra incorrect row returned when ?key= is
specified (was: Bug in _all_docs when en_GB.UTF-8 locale is used: extra
incorrect row returned when key is specified)
Removed locale from title of bug as the test case failed for rboyd too, who has
the en_US locale. The non-design-doc problem occurred for him as well.
> 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_test.diff
>
>
> 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.
