[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         | Thomas Jarosch <thomas.jarosch at intra2net.com>
 Summary            | Handling of composite fields during import
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             | Michael Rubinsky
+New Attachment     | turba-fix-composite-field-import-v2.patch
-----------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2008-06-11 12:42) wrote:

> 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.

Thanks, you are right, I didn't notice that code path before.

Attached is an updated patch to fix this issue. I also updated
the comment to be more precise about it.