Thanks Brendan! Currently local document is not in 2.0.0 API. As Jens said, it's not difficult to add APIs for it. We are taking the approach to have minimum set of the API as much as possible. We would like to hear from developers about what they need to build up a richer set of the API. I think we need a way for developers to give us feedback for 2.0 features. I will bring this up to our PM.
You can also simply emulate the local document by creating a new database only for storing data that you don't want to sync. By doing that you get the query feature (even now with 1.x) :) On Monday, March 27, 2017 at 11:09:52 AM UTC-7, Brendan Duddridge wrote: > > That would be awesome. A simple way to query based on keys would be great > too. Right now when I want to clear out a whole bunch of key/values from > the local document store I have to fetch regular documents, loop through > them, then delete the ones that have matching keys. I'm using this for > storing CloudKit sync metadata. When you receive a response from CloudKit, > it contains metadata that needs to be stored so that the next time you go > to sync, you can create a CKRecord that already has the metadata in it and > it knows to match it up with a CKRecord on the server. My keys all have a > prefix and it would be great to be able to delete them all in one go via a > prefixed search. But just the same local document store that we have today > would be great to still have in 2.0 (or 2.1 when you can get to adding back > geo queries). > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/a4fb9c6e-e408-4677-b39d-304794174e41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
