[Tickets #8130] Serialization issues with PHP 5 objects

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8130
------------------------------------------------------------------------------
  Ticket             | 8130
  Created By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Serialization issues with PHP 5 objects
  Queue              | Horde Base
  Version            | HEAD
  Type               | Bug
  State              | Assigned
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-03-30 21:18) wrote:

Using serialize() on a PHP 5 object is troublesome, since the  
representation of objects containing private/protected member  
variables includes null characters.  These NULL characters will  
truncate database insertion - at least using Postgres 8.3 in TEXT  
data.  We use TEXT data for things like prefs, sessionhandler, cache,  
and vfs.

See:
http://bugs.php.net/bug.php?id=29865
and
http://bugs.php.net/bug.php?id=45244
where the PHP folks claim this isn't a bug.

Possible solutions: vfs, sessionhandler, and cache should probably use  
binary data (BYTEA on postgres).  Not so sure about prefs, so we might  
need a different storage solution there (base64/json).