Julio Betta

Couldn't agree more with @tohagan. I've been using pouchdb and superlogin for a while... CouchDB/PouchDB/Superlogin are really awesome!

🤔 I'm facing pretty much the problem here #264 ... any updates on that? I know, 5 years... 🤣

I've solved this issue by removing `?limit=0&descending=true` from the line below. https://github.com/rnewson/couchdb-lucene/blob/5106b033ebfb248b9274eca1f4176cdb2e3d312b/src/main/java/com/github/rnewson/couchdb/lucene/couchdb/Database.java#L102 The timeout was happening because the `last_seq` returned from this method was always different from `update_seq` returned by...

Now I know the side effects... It degrades performance on large databases because it needs to load the entire `_charges` to get `last_seq`... 😩

For god's sake, let us get access to response.

The best thing we can do now is to fork the project, modify it as we need and add these lines to `composer.json`: ``` "require-dev": { "behat/web-api-extension": "dev-master" }, "repositories":...

I've started creating a file with constant values for each message. Then, on each response, I've added a `i18n` property, like this: ``` var c = require('./i18nKeys'); ... res.status(200).json({ ok:...

same here... did you solve this issue?