[Tickets #10803] Re: Errors in various variables with horde_db 1.1.2 & postgresql 9.1.1
bugs at horde.org
bugs at horde.org
Mon Nov 28 10:03:23 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/10803
------------------------------------------------------------------------------
Ticket | 10803
Updated By | ex_adres at yahoo.com
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 | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Slusarz
------------------------------------------------------------------------------
ex_adres at yahoo.com (2011-11-28 10:03) 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.
Thanks for the feedback.
As far as I know the server is working fine, the difference between
Horde working correctly or not is the downgrade from 1.1.2 to 1.1.1. I
have upgraded and downgraded again to check this.
With 1.1.1 the values stored appear differently in clear text
(a:2:{s:4:...) instead of the hex strings. As the only difference
between the two states is the version of the pear module and the
server appears to be working fine, I would not know where else to look
for the cause of this.
More information about the bugs
mailing list