[SyncEvolution] "Comparison was impossible" "

[Graham Cobb]

On 28/04/17 10:05, Patrick Ohly wrote:
> On Fri, 2017-04-28 at 10:31 +0200, Vincent wrote:
>> Could you tell me more about synccompare?
> 
> In the syncevolution.org packages, it is under /usr/bin/synccompare.
> It's a perl script that takes two database dumps and compares them,
> similar to a diff between text files.

I find it to be of variable usefulness. It is great when it works, but
in my experience it scales horribly. I have to have it completely
disabled on all my low-power systems (phones, etc) -- I have never had
it run to completion on my Jolla phone, even leaving it overnight, so I
just turn off comparison on those devices.

Even on higher power systems it sometimes gets very confused and mixes
up parts of different entries and ends up reporting all 2000 entries as
different! I have it mostly turned off except when testing to see if
changes are propagating as expected (or what changes are being lost as I
do some one-way syncs).

I think I always see "comparison was impossible" with refreshes. I
assumed that is because the databases are deleted or something (although
thinking about it further I am not sure that is a reasonable expectation).

Graham
_______________________________________________
SyncEvolution mailing list
SyncEvolution at syncevolution.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution