> On Sep 3, 2014, at 12:33 AM, Runar Jordahl <[email protected]> wrote: > > The way I read this is that Sync Gateway uses a Couchbase Server bucket as > its private storage. If you use Sync Gateway you need to deal with a > different API than the Couchbase Server API. Also, features of Couchbase > Server (like indexing & map-reduce) are not supported, or work different. > Basically you are now dealing with a different type of database, which > happens to use Couchbase Server to store its data.
Basically yes. This is inevitable because Couchbase Server (in its current form) doesn't support the type of metadata that's necessary to track document histories for replication. Modifying documents through the Couchbase Server API doesn't update that metadata, which messes up the Sync Gateway's tracking of histories. > So I get a better development experience at the client, but at the server I > cannot any longer use the strong libraries for connecting to Couchbase. There are a number of libraries <http://stackoverflow.com/questions/1050152/use-couchdb-with-net> for accessing CouchDB-compatible databases from .NET. > I wanted to use all features of Couchbase (replication, scalable storage, > indexes) and have server processes access it directly. Then parts of the data > should be replicated to clients using Sync Gateway. You should consider using bucket shadowing <http://developer.couchbase.com/mobile/develop/guides/sync-gateway/wcbs/bucket-shadowing/index.html>. —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/B3EF5E0F-32B3-4F8B-8503-069F62F14EC9%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
