Tickets :: Comment on [#8130] Serialization issues with PHP 5 objects (Postgres)

* Your Email Address
* Spam protection	Enter the letters below: . ,.__ .___.. ..__ \./ [__) _/ \|_/ [__) \| \| ./__.\| \\| \
Comment	> 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).
Attachment
Watch this ticket