On Thu, 2013-07-04 at 13:01 +0300, Patrick Ohly wrote: > Hello! > > I just noticed one aspect of the example configs that I wasn't aware of: > syncclient_sample_config.xml: <field name="PHOTO" type="blob" > compare="never" merge="fillempty"/> > > What I see in a slow is that if all fields are equal except for the > photo, the modified photo is not stored because merging considers it not > relevant (compare="never" => eqm_none). > > According to the doc: > "never": field is not compared at all. This is for fields that do not > contain user data, such > as "REV" in vCard. It would not make sense to compare these fields, > as they are not rele- > vant for finding out if two objects have the same data or not. > > > What was the rationale for using that mode for PHOTO? Is it for storages > which store photo data after re-encoding it? With such a storage, the > comparison would yield a false "field is different", causing unnecessary > writes. But with a storage that stores the data as-is, comparing it is > better (IMHO), because modified data actually gets stored. The downside > is that comparisons become more expensive.
When using compare="conflict" fot PHOTO, I get [2013-07-04 14:35:45.739] Winning and loosing Field 'PHOTO' not equal: '<BLOB size=0>' <> '<BLOB size=0>' [2013-07-04 14:35:45.739] - updated fields such that both have same value '<BLOB size=0>' and PHOTO == EMPTY in a script also does not work. Shouldn't a blob comparison compare the content (= byte string) and treat a blob of size 0 as empty? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
