pouchdb

I develop an app with Ionic where each user got its own PouchDB database synchronise with its own remote CouchDB database. I use couch_peruser=true so any user that want to access its database need to authenticate. This system is easy to do if we store the username & password locally or if we ask the user to give them anytime a sync is needed but none of these options are good (security concern or non user-friendly). I came with those two options, but none is working: 1) The best option that came to me was to use Cookie Authentication , just save the token locally and use it, but unfortunately

Very similar to these two CouchDB questions: 3311225 and 8924793 , except that these approaches don't allow partial matching . Having e.g. these entries: [{_id: 1, status: 'NEW', name: 'a'}, {_id: 2, status: 'NEW', name: 'aab'}, {_id: 3, status: 'NEW', name: 'ab'}, {_id: 4, status: 'NEW', name: 'aaa'}, {_id: 5, status: 'NEW', name: 'aa'}] and key [status, name, _id] There seems to be no way to filter these entries by status (full string match) and name (partial string match ~ startsWith ) order them by id paginate them because of the partial string match on name . The high value unicode

This is the situation: We have a series of users who share some documents. The documents they can share might change throughout the day, so can the documents themselves (changes and deletions). The users can change some information on the documents. E.g. Users | Documents A | X A | Y A | Z B | X B | Z C | Y Possible groups: A+C, A+B The server on CouchDB is a replica of a SQL Server DB with this data, an ETL takes care of managing changes on CouchDB. However, the CouchDB database is replicated on each user phone via PouchDB. The goal: To replicate changes and deletions accordingly. What we've

Is it possible to manage the sync conflicts from the client? What I mean is, when pouchDB does a sync and detects a conflict, is it possible to get the local doc PouchDB is trying to sync and the last revision of CouchDB doc? If I can get both docs, I can display them to the user and he can choose which version to keep... nlawson You're in luck, because this is exactly the problem CouchDB and PouchDB were designed to solve. Basically you can read up on the CouchDB docs on conflict resolution . Everything in there should also apply to PouchDB. (If it doesn't, it's a bug. ;)). The CouchDB wiki

I know views can be built using complex keys (an array basically). But, do normal documents also support that? I want to avoid views as performance on phones can be very slow with many many docs. So I'm using the "Use and abuse your keys" approach. So that is why I would need complex keys so I can use startkey and endkey on those. Yep, it's totally possible. Read this blog post , skip to "use and abuse your doc ids." Basically what you do is use the PouchDB Collate plugin to serialize your complex key into a string, and then use that for the _id . Then lookups work exactly the same as with the