Multi-master conflict = same primary key changed on two or more servers
Built-in method: latest wins (all txns across all databases)
Custom methods: you decide, but there can be only one winning database
Not needed the great majority of the time!
Exceptions and conflict handlers are two examples
Can also run before the sync, before the copy, after copy, after sync
After-sync is handy for cache invalidation
Before-sync can even tell the sync not to run: like an advanced trigger
> This is part of the answer.
> > If there is a conflict, then either the standard conflict handler, or a
> > custom one, set per table, is run to sort things out.
> At least for data.
> Gnumed-devel mailing list
> Gnumed-devel@gnu.... > https://lists.gnu.org/mailman/listinfo/gnumed-devel