[
https://issues.apache.org/jira/browse/COUCHDB-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908717#comment-13908717
]
Robert Newson commented on COUCHDB-2065:
----------------------------------------
Hi Nolan,
I'm certainly mindful that CouchDB is pretty sweet and that not everyone uses
it specifically because it solves offline replication problems well. We do want
to see CouchDB used in other ways without confusing or diluting that central
message. The main proposal we've seen is a bit more modularization. To be
specific, the database core (couch_file, couch_db, couch_btree) should be
extracted into its own app to allow CouchDB variants to reuse that code but
with different semantics (like the ones you describe). It won't be CouchDB, but
it would be "powered by CouchDB core", and I'm all for that. Agree that on a
single-user device like a phone or tablet that some parts of full-blown CouchDB
don't make sense.
> Overwrite a document with a single request
> ------------------------------------------
>
> Key: COUCHDB-2065
> URL: https://issues.apache.org/jira/browse/COUCHDB-2065
> Project: CouchDB
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Reporter: Nolan Lawson
>
> It would be convenient to have the option to overwrite documents with a
> single request, rather than having to GET, check the _rev, POST/PUT, possibly
> deal with conflicts, and then continue POST/PUTing until success. It could
> be something as simple as:
> {code}
> PUT localhost:5984/mydb/mydoc?force=true
> {code}
> If two callers attempt to update the same document at the same time, whoever
> gets there last would win.
> Prompted by a [discussion in
> PouchDB|https://github.com/daleharvey/pouchdb/issues/1388].
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
