From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Christopher A Hotchkiss <christopher(dot)a(dot)hotchkiss(at)jpmchase(dot)com>, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Trigger Display Bugs in 1.12 pgAdmin |
Date: | 2010-09-25 06:31:04 |
Message-ID: | 4C9D9728.4090504@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Le 25/09/2010 01:09, Dave Page a écrit :
> On Fri, Sep 24, 2010 at 11:54 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>
>> Much better. So, the only way to fix this, AFAICT, is to set bytea_ouput
>> to "escape" when connected to a 9.0 server. My question is this: should
>> I set the parameter at the connection start, or should I set and unset
>> it during the search of triggers? The latter is less error prone, but
>> requires to execute three more queries (SHOW bytea_output, SET
>> bytea_output TO escape, SET bytea_output TO old_value).
>
> Please set at connection. The old output is what all the rest of the
> code expects (if anywhere does expect it), so I can't imagine it would
> break anything.
>
OK, that was also my favorite solution. Just pushed my commits on 1.12
and master.
Thanks.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2010-09-25 07:07:01 | Re: Connection color is not correctly changed in query windows connection drop-down. |
Previous Message | Jeremy Palmer | 2010-09-24 23:18:23 | Re: Can not debug plpgsql using PgAdminIII |