[Tickets #12506] Re: Contacts sync with ActiveSync get duplicates and not sync

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12506
------------------------------------------------------------------------------
  Ticket             | 12506
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Contacts sync with ActiveSync get duplicates and not
                     | sync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-08-12 19:52) wrote:


> Well, maybe but if you look directly into database, I see this by example.
>
> When imported from VCard file:
>> select object_anniversary,object_workemail,object_homeemail from  
>> turba_objects where object_firstname='TEST';
> +--------------------+------------------+------------------+
> | object_anniversary | object_workemail | object_homeemail |
> +--------------------+------------------+------------------+
> | NULL               | NULL             | NULL             |
> +--------------------+------------------+------------------+
> 1 row in set (0.00 sec)
>
> When added manually through Turba web:
>> select object_anniversary,object_workemail,object_homeemail from  
>> turba_objects where object_firstname='TESTMANUAL';
> +--------------------+------------------+------------------+
> | object_anniversary | object_workemail | object_homeemail |
> +--------------------+------------------+------------------+
> | NULL               |                  |                  |
> +--------------------+------------------+------------------+
> 1 row in set (0.00 sec)


This is because the UI form actually contains those fields. When  
imported, and the fields are not present, the hash does not contain  
those fields and the default for those fields in the DB is null. The  
duplicate detection still works in this case. So, unless you see some  
unwanted behavior because of this, I'll still consider this ticket  
resolved.