couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-858) GET /db/_design/doc/_info should not trigger an update
Date Wed, 18 Aug 2010 19:42:16 GMT

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

Adam Kocoloski commented on COUCHDB-858:
----------------------------------------

Other way around, an update is only triggered when the group is _not_ already open.

I think we should not fire off an update when initializing a group.  That's a very simple
change, and addresses this ticket.  But perhaps users would prefer the same freshness options
for _info that are available for _view.

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