[exim-dev] [Bug 508] PostgreSQL client_encoding broken

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Casey Allen Shobe
Datum:  
To: exim-dev
Betreff: [exim-dev] [Bug 508] PostgreSQL client_encoding broken
------- You are receiving this mail because: -------
You are the QA contact for the bug.

http://bugs.exim.org/show_bug.cgi?id=508




--- Comment #11 from Casey Allen Shobe <cg@???> 2015-01-18 19:19:32 ---
Talked with Andrew Gierth (RhodiumToad) briefly this morning...

Setting client_encoding to SQL_ASCII is effectively setting it to be the same
as the server encoding.

A bytea type field could be used to store bytes directly, and he suggested that
Exim could store data into bytea fields using Base64 encoding.

However storing data into a bytea would require the text form of a bytea to be
supplied, which in recent PG versions is either octal escapes or \x followed by
a hex string, e.g. '\x000001010202'.

Perhaps something like "insert into foo (bytea_column) values
(decode('${str2b64:$h_Subject}', 'base64'))".


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email