Hello Patrick,
On 11 Jul 2014, at 15:27, Patrick Ohly patrick.o...@intel.com wrote:
I'm currently investigating why a comparison of two PHOTO fields of
different length returns field equal. PHOTO is defined as:
field name=PHOTO type=string compare=conflict merge=fillempty/
My first
On Mon, 2014-07-14 at 18:15 +0200, Lukas Zeller wrote:
Hello Patrick,
On 11 Jul 2014, at 15:27, Patrick Ohly patrick.o...@intel.com wrote:
I'm currently investigating why a comparison of two PHOTO fields of
different length returns field equal. PHOTO is defined as:
field
Hello Patrick,
the patch is fine, anyway!
Regarding differences between blob and string when it comes to compare
On 14 Jul 2014, at 20:10, Patrick Ohly patrick.o...@intel.com wrote:
My first question would be why PHOTO was defined string here, not blob?
I changed that in this commit:
Hello!
I'm currently investigating why a comparison of two PHOTO fields of
different length returns field equal. PHOTO is defined as:
field name=PHOTO type=string compare=conflict merge=fillempty/
I think the specific situation is that the two values contain a null
byte somewhere in the
