[Tickets #10803] Re: Errors in various variables with horde_db 1.1.2 & postgresql 9.1.1

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10803
------------------------------------------------------------------------------
  Ticket             | 10803
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Errors in various variables with horde_db 1.1.2 &
                     | postgresql 9.1.1
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-11-27 13:56) wrote:

> Instead of the correct values strings appear with contents like:  
> '\x613a323a.....' (hex coded ascii I assume)

This is exactly what is expected to be stored .  These values should  
be automatically converted when querying the DB by the PDO layer.   
Sure enough, NO code has changed involving *decoding* of the value  
from Postgresql from 1.1.1 to 1.1.2.  So your bug report doesn't make  
sense.

The only thing that has changed is the format of the data we pass to  
Postgresql.  But the unit tests verify this is working fine on a 9.1.1  
server.  So you should try running the Postgresql DB unit tests to see  
if they pass on your server.