You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the readme 'To merge these "conflicts" back into a single value, use osm.put(id, doc, cb) to store the desired document value.'
How do you update a doc that has a fork without merging? I can think of several scenarios where a user would need to update a forked doc (i.e. update one of the forks) and postpone dealing with merging / resolving conflicts.
The text was updated successfully, but these errors were encountered:
You can give put() an array of opts.links to point back at. If opts.links isn't defined, the default value is the most recent set of updates. This behavior is documented in hyperkv, but the explanation could be moved inline into the osm-p2p-db docs.
ghost
pushed a commit
that referenced
this issue
Jan 19, 2016
From the readme 'To merge these "conflicts" back into a single value, use
osm.put(id, doc, cb)
to store the desired document value.'How do you update a doc that has a fork without merging? I can think of several scenarios where a user would need to update a forked doc (i.e. update one of the forks) and postpone dealing with merging / resolving conflicts.
The text was updated successfully, but these errors were encountered: