Yes, I am converting my Core Data app to CBL. I have a downloader class that gets my CouchDB data via a passthrough server that checks credentials. I am also HIPAA-compliant so it 'requires' a separation of the db server from the public so I can't expose CouchDB to the public. I have a route in my Node.js server that gives me the changes from the private CouchDB server . I track the 'lastSequenceNumber' in my app and request changes since that on launch. So I get the CouchDB data from the Node.js server and want to put it into CBL. So I have to preserve the _id and _rev properties of each document so that I can update them back on the server.
If I cannot save a document with the _rev matching my incoming data, CBL won't work for my use case. Unless I use replication and design the routes on my Node.js server to match the replication protocol. But I assume I would have to mimic ALL of the protocol, including the handshaking, etc. Is this correct? On Monday, February 10, 2014 3:50:53 PM UTC-8, Jens Alfke wrote: > > > On Feb 10, 2014, at 3:06 PM, Alan McKean <[email protected] <javascript:>> > wrote: > > > Creating doc with [database documentWIthId::”....”]. All good. But if I > keep the _rev in the dictionary when I putProperties, it fails. Take the > _rev out, and it succeeds but sets the _rev to 1-xxxxxx. Is there a way to > preserve the _rev property I get from the server? > > What do you mean by "the _rev property I get from the server"? Are you > trying to transfer documents without using the replicator, somehow? > > The "_rev_ property is created and managed internally. Ordinarily you have > no control over it and should just ignore it. > > —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/424bb783-5cc2-4eab-9dfa-0d6445634cd6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
