Re: [pgadmin-support] Trigger Display Bugs in 1.12 pgAdmin

2010-09-24 Thread Guillaume Lelarge
Le 25/09/2010 01:09, Dave Page a écrit : > On Fri, Sep 24, 2010 at 11:54 PM, Guillaume Lelarge > 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

Re: [pgadmin-support] Can not debug plpgsql using PgAdminIII

2010-09-24 Thread Jeremy Palmer
Late follow-up on this email! Can anyone give any help? Has it been resolved in 1.12? From: Jeremy Palmer Sent: Tuesday, August 03, 2010 3:02 PM To: pgadmin-support@postgresql.org Subject: Can not debug plpgsql using PgAdminIII I'm trying to debug plpgsql functio

Re: [pgadmin-support] Trigger Display Bugs in 1.12 pgAdmin

2010-09-24 Thread Dave Page
On Fri, Sep 24, 2010 at 11:54 PM, Guillaume Lelarge 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

Re: [pgadmin-support] Trigger Display Bugs in 1.12 pgAdmin

2010-09-24 Thread Guillaume Lelarge
Hi, Le 24/09/2010 21:26, Christopher A Hotchkiss a écrit : > To Who It May Concern, > I am using the new 1.12 pgAdmin on Windows XP SP3 and I have notice two > display inaccuracies when connecting to a Postgres 9 database. > > For example when creating the following trigger: > > CREATE TRIGGER

[pgadmin-support] Trigger Display Bugs in 1.12 pgAdmin

2010-09-24 Thread Christopher A Hotchkiss
To Who It May Concern, I am using the new 1.12 pgAdmin on Windows XP SP3 and I have notice two display inaccuracies when connecting to a Postgres 9 database. For example when creating the following trigger: CREATE TRIGGER c_aud_trg BEFORE INSERT OR UPDATE OR DELETE ON ca FOR EACH ROW

Re: [pgadmin-support] dropping connection

2010-09-24 Thread Michael Shapiro
I am running the latest release for Windows (XP) -- 1.12.0 (Sep 17, 2010). The SQL query window lost the connect, failed to reestablish it, and PgAdmin crashed when I ran the query 2 more times. I had run a query that took about 10 minutes to complete. It completed. Then I stepped away for a while

Re: [pgadmin-support] Graphical Query Builder -- expanding public requires annoying double click

2010-09-24 Thread Dave Page
On Thu, Sep 23, 2010 at 9:34 PM, Guillaume Lelarge wrote: > Le 23/09/2010 22:31, Dave Page a écrit : >> On Thu, Sep 23, 2010 at 9:27 PM, Peter Dietz wrote: >>> Hi All, >>> I have a minor grievance with pgAdmin3's Graphical Query Builder. >>> I click plus on Schemas, then public has no plus, so I

Re: [pgadmin-support] Graphical Query Builder -- expanding public requires annoying double click

2010-09-24 Thread Bob McConnell
From: Guillaume Lelarge > Le 23/09/2010 22:37, Thom Brown a écrit : >> On 23 September 2010 21:31, Dave Page wrote: >>> On Thu, Sep 23, 2010 at 9:27 PM, Peter Dietz wrote: Hi All, I have a minor grievance with pgAdmin3's Graphical Query Builder. I click plus on Schemas, then publi

Re: [pgadmin-support] Connection color is not correctly changed in query windows connection drop-down.

2010-09-24 Thread Valentine Gogichashvili
Hallo Guillaume, I can reproduce this the following way: 1. Create 2 database connections in the tree and choose color for the first connection and a different color for another one (red for the first and gray for the second one) 2. Go to the first database (red one) and open a Query Window (the

Re: [pgadmin-support] pgAdmin linking to the wrong pg_dump

2010-09-24 Thread Cousin Florence
> -Message d'origine- > De : pgadmin-support-ow...@postgresql.org > [mailto:pgadmin-support-ow...@postgresql.org] De la part de Dave Page > >> Hi there, > >> > >> Go to File -> Options, and on the "General" tab look for "PG bin > >> path" - enter the correct path here. > >> > > > > And,