I would like to store all the data used in my app inside the same database. However, some of the information I may not want to sync. back to the server.
As an example I would like to create a “Configuration” document that would hold various user specific settings related to e.g. the user interface (could be language selected by the user). But I don’t really want to sync. that info back to the server (in this case I would have one “Configuration” document for EACH user in the system - so not even a unique key).
I appreciate that I can test for “write access” in the sync formula on the sync gateway - but I already know that this data shouldn’t be sync’ed - so is there a way to tell the local replicator not even to bother sending the information as we know it will be rejected - so we can avoid using the extra bandwith?