[Tickets #11452] Re: content of 'turba_objects' -> 'object_member' yields to error

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/11452
------------------------------------------------------------------------------
  Ticket           | 11452
  Aktualisiert Von | piper at hrz.uni-marburg.de
  Zusammenfassung  | content of 'turba_objects' -> 'object_member' yields to
                   | error
  Warteschlange    | Turba
  Version          | 3.0.15
  Typ              | Bug
  Status           | Feedback
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


piper at hrz.uni-marburg.de (2012-10-15 09:07) hat geschrieben:

The problem seems to be located in turba/lib/Driver/Sql.php, the  
search-function there does not recognize the '__members'-value  
returned from postgresql as blob and therefore does not use  
'binaryToString()' on it.

I found a workaround by setting the turba-attribute 'type' => 'image'  
for '__members' in turba/attributes.local.php, this forces the use of  
'binaryToString' on the '__members'-value, which is then recognized  
and used correctly. This solution works for my setup with postgresql  
as only source of contact-lists, but will not work if contact lists  
come from other sources too, e.g. LDAP.

I assume, the correct solution has to be somewhere in the  
postgresql-driver when handling bytea-values, but I do not know enough  
of php for finding it.

Andreas