Hello, I am a Dutch user of CouchDB for quite some time. I know I won't make headlines, given that I only run a single-node CouchDB instance that runs on a small VPS that also runs my small web-applications as well (my DB's are only up to dozens of MBs in size), but that wouldn't stop me from mailing the mailing list :)
Recently upgraded my CouchDB 2 instance to the latest 3 version, it was about time... It was an easy process and v3 seemingly fixed some bugs that were plaguing me, so I am happy with my choice. I was mostly wondering how others are using their CouchDB setup, so that's why I am writing. I have some questions to the community in general: Coming late to the CouchDB party (around the v2 days), Mango querying is one of my favorite features. Tutorials/videos always seem to talk about JavaScript filters functions and dismiss Mango as a minor, unimportant feature (IF they mention Mango at all). Was just wondering how long-time users are querying their JSON documents mostly nowadays? I saw somewhere in the v3 release notes that the Javascript "update" functions were deprecated in v3, although I didn't see a Deprecation warning in the https://docs.couchdb.org/en/stable/ddocs/ddocs.html#updatefun section. Is it indeed deprecated? I kinda liked that feature, for example to update creation/update timestamp fields in documents automatically. Am I correct in thinking that CouchDB is moving away from the idea that web applications should run on top of CouchDB (since I use Nginx, I personally never even considered it) and logic like updating timestamps, should, according to the CouchDB devs, ideally be implemented in the client applications themselves? Also, are "Validate Document Update Functions" also part of the "Update functions" that are deprecated? Are members of this mailinglist using custom Query Servers in practice and if so, what are your use-cases? It seems so interesting and I wonder what people are doing with it. Finally, one of the limitations that I know of, that deleted documents stay in the CouchDB database "forever", is one that stops me from choosing CouchDB for some applications, that have to deal with temporary data. Is that limitation still in place (now and/or for the foreseeable future?). To the CouchDB team members, past and present: many thanks for your efforts! I wish I was more familiar with Erlang and could contribute somehow. Kind regards, Vincent
