couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aju <>
Subject Re: put and no _rev
Date Fri, 06 Mar 2009 19:24:04 GMT
Jason Smith wrote:
> aju wrote:
>> in a RDBMS when you update an existing row (document) it is a single 
>> step. (there's no revision term here obviously). likewise in 
>> subversion when you commit an updated document it is a single step.
> Well in a RDBMS if you have a common constraint like uniqueness on a 
> column, you have to decide whether to INSERT or UPDATE.  So most likely, 
> you will grab a big lock, SELECT something, process the data, INSERT or 
> UPDATE, then release the lock.  So that's two queries as well.

you are right. probably bad example, but i still can't see the argument
for not just updating a document based on the latest revision. how can 
it hurt?

hmm, or perhaps instead one could specify a special rev value "latest"

	PUT /somedatabase/some_doc_id?rev=latest


View raw message