Re: Batch mode options for CouchDB 4.0

Given that 4.0 is not one, but two major versions away from 2.X, what is the reason to just not deprecate this behavior and remove it entirely? 4.0 probably wouldn’t be out for another year at least and deprecating information can be included in 3.0 once out. I see no reason to include things

Re: Getting started on CouchDB 3.0, and an introduction

if you wanna help, we can always do with more release engineering help :) Best Jan — > On 7. Aug 2019, at 18:05, Tabeth Nkangoh wrote: > > Hello all! > > > I would argue that in addition to #1534, #1524 should definitely be part of > 3.0. The ability to control who has

Re: Getting started on CouchDB 3.0, and an introduction

Hello all! I would argue that in addition to #1534, #1524 should definitely be part of 3.0. The ability to control who has access to certain documents is something most users would expect in 2019 at this point. Right now there's really no way to do this without putting a convoluted proxy to ac

Re: [DISCUSS] A direction from a non-contributor

This has been an interesting thread. To share my two cents, I would say I'm strongly opposed to CouchDB moving in any direction "IoT" at this time for several reasons: 1. CouchDB is designed intentionally to be eventually consistent. Eventual consistency is not desirable here. In fact, bein

Re: CouchDB and future

Hello all, After reading the documentation and this thread I propose the following formula to document officially for determining the Q and N values. To start, as currently documented, N should be set to the number of nodes. This muc

[DISCUSS] Session token invalidation

Hello all, my name is Tabeth and this is my first post. Please let me know if I'm not following any conventions surrounding the usage of this mailing list. Without further ado: I believe it would be prudent for CouchDB to add the ability to invalidate specific sessions. There was some discussio