maas-devel team mailing list archive

[Stuart Bishop <stuart.bishop@xxxxxxxxxxxxx>]

On Tue, Sep 25, 2012 at 8:15 PM, Jeroen Vermeulen <jtv@xxxxxxxxxxxxx> wrote:
> On 2012-09-24 14:34, Stuart Bishop wrote:
>
>> Do you recall the problem with bytea btw? The SSO systems needed to
>> set 'bytea_output=escape' in postgresql.conf (or in the session, or
>> with ALTER DATABASE) to get bytea fields working with Django.
>
>
> Is that related to the new hex-escaping format in postgres 9?
>
> My memories about this have faded, but IIRC we came to a stage where it
> might _seem_ to work, but with raw binary data being passed off as text.
> Might not have caught the problem without some very specific tests.
>
> I believe there was also the complication that when you write your own
> column type in django, your custom conversion functions can receive values
> that need converting, or values that have already been converted.  They
> won't know which.  But I guess there's ways around that.

There are. Ask in #isd for the details, they are using bytea with
Django and we had to twiddle settings for things to keep working with
PG 9.1.


-- 
Stuart Bishop <stuart.bishop@xxxxxxxxxxxxx>