Hello again,...
I want to add something that I think I forget. I mention that the PouchDB appear more or less easy, and, it's truth from some point of view, but, that API is also more or less complex (like any other API, of course), so we can / must deal with callbacks, for example, that, depending on our app, we need to use or not.
For example, and, as you can see in the sample, the "sync" method have various events or callbacks that we can / must use. And the same can be said about other methods, like who insert new registries in the database: this callbacks have their own arguments, etc. We can or must use that callbacks, arguments, etc., in order to properly work with the database.
We can't expect, for example, that everything work like expected, so we must take care about the available errors callbacks, the available error codes, etc., in order to assert that the app's user is informed if a registry can't be inserted, if we can't sync to the database, etc., etc. It's a question of time of work, to study and finally handle the PouchDB API, and also how to present or require the user's input from AB, etc.
So take it with time, Peter. :-) And, of course, don't hesitate to post in this forum if you have some specific problem.
Posts by DecSoft