Tickets :: Comment on [#10919] Postgresql 9.0 bytea output is hex and should be escape

* Your Email Address
* Spam protection	Enter the letters below: .___..__.. ,.__..__ \| \| \| \./ \| \|[__) \| \|__\| \| \|__\\|
Comment	>>> In PostgreSQL 9.xx bytea values have hex as default output, but horde >>> expects escape. >>> (http://www.postgresql.org/docs/9.0/static/release-9-0.html) >> >> No. We don't expect anything. PDO handles result parsing. > > This is not true, at least not in current code. > >> We have unit tests that test exactly this and they work fine. >> >>> With "ALTER DATABASE horde SET bytea_output = 'escape'; " you can >>> change the output postgresql uses. >> >> No. We don't care what the output is - that is for PDO to worry >> about. The only thing we care about is how to insert data into the >> DB. And as is clearly discussed from that above page: > > Not true. The database returns the data either as hex data, or > escaped octal depending on the server's bytea_ouput setting. We > expect the later. See > Horde_Db_Adapter_Postgres_Column::binaryToString(). In Postgres 9.x, > with bytea_output set to 'hex' (the default in Postgres 9) the regexp > will NOT match. PDO doesn't care what the value of this setting is, > it returns it as -is. > >> The bytea type always accepts both formats on input, regardless of >> this setting. > > Yes. It accepts the data for WRITING regardless of the setting, but > it will presented back to client code differently depending on the > setting. Using an ALTER database statement is one way to fix, but > another is to provide "options: --bytea_output=escape" in the > connection string. >
Attachment
Watch this ticket

Saved Queries