| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| 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-24 23:09:26 |
| Message-ID: | AANLkTimkhptj1zU3dxkYVcPe39m3mhEu_iKWiAJ0rGiM@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Palmer | 2010-09-24 23:18:23 | Re: Can not debug plpgsql using PgAdminIII |
| Previous Message | Guillaume Lelarge | 2010-09-24 22:54:02 | Re: Trigger Display Bugs in 1.12 pgAdmin |