I’m starting work on a project that has a need for company provided content with user supplied “attached” content. An analog to this project would be:
My recipes 1. There is a master recipe database that is published and replicated from the company’s Couch* database. It has the recipe and related tags on a single document (myrecipe). Alternately, we may separate the recipe and tags into separate docs. 2. The user can then add their own tags that are not necessarily shared with the company or community, they are their own tags per document. 3. Potential feature but not in v1: The user can replicate tags among their copies of the program using the company’s replication server (using some variation of the “each user has their own database” solution). I’m torn on how to do the user tags. I see two options: Option 1: User tags are stored in the main CBL database in separate documents (userTag with a “relationship” to the myrecipe document). For feature #3, build a filtered push replication for the userTag documents. Option 2: Build a separate CBL database for the userTag documents. This makes replication easier, but marrying the tags between the user and company provided data seems difficult. I don’t see any version of SQLlite’s “ATTACH” functionality in CBL’s documentation (and I’m not sure it even makes sense). Any suggestions on the right path? Thanks! -- 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/37E41765-D104-42A9-84F9-087A7E2DE7C9%40gmail.com. For more options, visit https://groups.google.com/d/optout.
