Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <24129221.60411286653962570.JavaMail.jira@thor>
Date: Sat, 9 Oct 2010 15:52:42 -0400 (EDT)
From: "Paul Joseph Davis (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-529) Avoiding updating a doc's _rev if
 nothing changed
In-Reply-To: <1265799715.1255621111502.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paul Joseph Davis updated COUCHDB-529:
--------------------------------------

    Skill Level: Committers Level (Medium to Hard)

> 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.
-
You can reply to this email to add a comment to the issue online.