Ah thanks. I just meant whether we needed to write additional network code that first uses the Sync REST API to send the existing data first, or whether the native ios push/pull replication code would work for previously existing ios databases and we just merely need to "turn it on" and point it to our server. This clarifies that.
Cheers, Ragu On Saturday, April 19, 2014 7:30:48 PM UTC-7, Jens Alfke wrote: > > > On Apr 19, 2014, at 6:40 PM, Ragu Vijaykumar <[email protected]<javascript:>> > wrote: > > However, if I release a CouchbaseLite ios app to the appstore that only > works to store data locally, can I later sync databases created on > the mobile apps to a server without using the Sync REST API? Is there > anything special that I need to configure so they can later be > synced properly? > > > I’m confused by the word “without” there. Was that a typo? You can > *always* sync a database from Couchbase Lite to the gateway (or to > CouchDB for that matter.) It uses the sync API, of course. > > What the docs are saying is a warning for people who are already Couchbase > *Server* users and have buckets containing data they now want to sync > with mobile clients. Unfortunately those buckets can’t be used directly as > Sync Gateway storage because they don’t have the right metadata. That > warning has nothing to do with Couchbase Lite. > > —Jens > -- 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/4c7e5b7c-11c6-4ab1-b1fc-cecfc723cd6a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
