[Tickets #6900] Re: Handling of composite fields during import

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6900
-----------------------------------------------------------------------
 Ticket             | 6900
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Handling of composite fields during import
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2008-06-11 12:08) wrote:


> It sets $hash[$key] which points to the composite field, not the
> individual part.


Yes, but follow the code in toDriverKeys() through some more and you'll
see that if we are not saving the composite field to storage (in other
words, if $this->map[$key]['attribute'] is empty) then the composite field
is parsed out into it's individual fields, and then *those* values are
saved to the $fields array when the arrays are merged.

To test this, just try to add a new contact in the "out of the box"
localsql source using Turba's UI....it nulls out all the individual name
fields.