couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COUCHDB-529) Avoiding updating a doc's _rev if nothing changed
Date Fri, 01 Jul 2011 21:03:28 GMT

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

Randall Leeds resolved COUCHDB-529.
-----------------------------------

    Resolution: Won't Fix

No activity in almost nine months.
Last comment suggests it's prohibitively expensive to implement this logic.

> Avoiding updating a doc's _rev if nothing changed
> -------------------------------------------------
>
>                 Key: COUCHDB-529
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-529
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: Database Core
>            Reporter: Matt Goodall
>
> Would it be possible for CouchDB to use its deterministic rev algorithm to avoid writing
changes to the database if nothing has actually changed in the doc that is sent for update.
> The most obvious use case is the user who clicks an HTML form's submit button, instead
of using the back button, when they haven't changed anything. I suspect most applications
do not check if the user made any changes and therefore end up sending exactly the same data
back as an update ... unnecessarily creating a new document rev, growing the database, invalidating
views, triggering _changes updates, etc.
> If CouchDB could determine that the new document is the same as the old document then
it could avoid writing to disc and return the current _rev in the response.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message