couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-858) GET /db/_design/doc/_info should not trigger an update
Date Mon, 25 Oct 2010 15:07:24 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924585#action_12924585
] 

Filipe Manana commented on COUCHDB-858:
---------------------------------------

Hi Klaus,

The patch looks very good to me. Just 2 remarks:

1) avoid changing unnecessarily (white space only) the following line:

_id:"_design/test", // turn off couch.js id escaping?


2) In the test, avoid using an hardcoded Etag value. Just store the previous and current values
and then compare them in the assertion

3) Don't forget the semicollons at the end of all your JavaScript lines (aparently some browsers
are picky about it).

> GET /db/_design/doc/_info should not trigger an update
> ------------------------------------------------------
>
>                 Key: COUCHDB-858
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-858
>             Project: CouchDB
>          Issue Type: Bug
>         Environment: All
>            Reporter: mikeal
>         Attachments: 0001-Fixes-COUCHDB-858.patch
>
>
> Ran across this in my futon rewrite.
> A call to the info for a ddoc triggers an update in some cases. koco says it's when that
"group is open". 
> This request needs to either not trigger an update or respect stale=ok.

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