pouchdb 复制冲突解决与远程胜利
pouchdb replication conflict resolution with remote wins
我正在尝试实施服务器修订覆盖本地修订的解析策略。 replicate().on('change', ..
上的 arg 看起来像
{
_id: "xyz",
_rev: "2-efg",
_conflicts: [
{
_id: 'xyz',
_rev: '2-mon'
有没有办法知道对象本身是本地的(调用复制的地方)还是远程的,以及 _conflicts
数组对象是否是远程的?
来自couchdb wiki 这是不可能的。
Another thing to notice is that peers do not have to be configured or tracked. You can do regular replications to peers, or you can do one-off, ad-hoc pushes or pulls. After the replication has taken place, there is no record kept of which peer any particular document or revision came from.
我正在尝试实施服务器修订覆盖本地修订的解析策略。 replicate().on('change', ..
上的 arg 看起来像
{
_id: "xyz",
_rev: "2-efg",
_conflicts: [
{
_id: 'xyz',
_rev: '2-mon'
有没有办法知道对象本身是本地的(调用复制的地方)还是远程的,以及 _conflicts
数组对象是否是远程的?
来自couchdb wiki 这是不可能的。
Another thing to notice is that peers do not have to be configured or tracked. You can do regular replications to peers, or you can do one-off, ad-hoc pushes or pulls. After the replication has taken place, there is no record kept of which peer any particular document or revision came from.