Hi all,
Just wondering if this is expected behaviour.
When using COPY with _local documents and the Destination header contains a
document identifier that does not start with _local then the document
appears to be copied without the copied document identifier starting with
_local/, ie, the
Hi everyone,
if you want to submit a link for this week's CouchDB Weekly News, please send
it to this thread until thursday, August 28, 11am UTC+2.
I'd especially invite you to submit content for the sections
- Releases in the CouchDB Universe
- Opinions, Talks, …
- Events
- Time to relax
It's the lowest layer so to say, for documents where any history is needed
it will be kept either in the living revision of the document or a 2nd
document.
I just wanted a general approach to get the documents out of the users db,
and thats the only purpose of the deleted revisions.
Thank you,
Hi Lena,
I have one think mentionable: we are currently testing the 1.6.1-rc4
release
http://markmail.org/search/?q=couchdb+1.6.1#query:couchdb%201.6.1+page:1+mid:7yz7a6rqfvr7ayrs+state:results
Thanks :)
Cheers
Andy
P.S.: Will you be around at JSConf in B?
On 27 August 2014 09:01, Lena
Heya,
I implemented COPY and I was definitely not taking _local docs into
any special consideration, so any behaviour is purely accidental :)
As far as I can tell, COPY just does what it tells you to do: It copies
a document from one URL to another. It is up to you to ensure that the
destination
obligatory comment that _bulk_docs is not an atomic commit across all the
documents, even with all_or_nothing:true. How much does this scheme break if
one or both of your updates introduce a losing conflict?
B.
On 27 Aug 2014, at 08:30, Stefan Klein st.fankl...@gmail.com wrote:
It's the
