[Syncevolution-issues] [Bug 4631] Google: ORG data is not consistent after two-way/slow sync between seperately updated client and server
http://bugzilla.moblin.org/show_bug.cgi?id=4631
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |P2
Status|NEW |ASSIGNED
Component|SyncEvolution |SyncML
Target Milestone|--- |future
--- Comment #5 from pohly <patrick.ohly(a)intel.com> 2009-07-23 04:20:19 ---
(In reply to comment #4)
(In reply to comment #2)
> The current behavior is consistent with Evolution, so we shouldn't change the
> config. As to handling the duplicate ORG, we already pick the later one. I'm
> not sure whether the order is predictable, but it doesn't matter anyway: there
> is no good solution for preserving both pieces of information, neither on the
> client nor on the server.
> I tend to close this issue as "works as intended".
I agree that not preserving both pieces of information, the problem is that it
will confuse end user because client and server show different company
information.
We might change the config so that the ORG field list is not overwritten.
Assuming that Google always displays the first ORG property, this would ensure
that we pick the same one.
Hmm, I was thinking of the "overwriteempty" config option, but it doesn't
quite
fit. We would need a "overwritenonempty=false" config option.
Congwu, can you look into this? I don't think it is urgent.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.