couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-196) Bug in _all_docs: extra incorrect row returned when ?key= is specified
Date Wed, 07 Jan 2009 23:38:44 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Anderson updated COUCHDB-196:
-----------------------------------

    Attachment: collation_ids.diff

I've attached another patch (really just a snapshot of my working setup, with debug logging
in the erl files and console.log in the tests)

It does indeed seem that collation by id is playing by different rules than collation by view
key. I'm not done investigating this yet, but I agree, we should get to the bottom of it.

> 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
>
>
> 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.


Mime
View raw message