Thread: Two bugs in pgAdmin3 1.0.0

Two bugs in pgAdmin3 1.0.0

From
Christopher Kings-Lynne
Date:
1. When you change the statistics target of a column, eg:

ALTER TABLE foo ALTER COLUMN bar SET STATISTICS 1000;

It is not reflected in the 'code view' for the column object.

2. On WinXP, using pgAdmin 3 1.0.0 and connecting to Cygwin pgsql 7.3.4, 
I get these message while connecting to the server:

FATAL:  unsupported frontend protocol
FATAL:  unsupported frontend protocol
FATAL:  unsupported frontend protocol
FATAL:  unsupported frontend protocol
FATAL:  unsupported frontend protocol

Cheers,

Chris



Re: Two bugs in pgAdmin3 1.0.0

From
Andreas Pflug
Date:
Christopher Kings-Lynne wrote:

> 1. When you change the statistics target of a column, eg:
>
> ALTER TABLE foo ALTER COLUMN bar SET STATISTICS 1000;
>
> It is not reflected in the 'code view' for the column object. 


We don't have statistics as property at the moment, do we need this?
If so, that's a TODO item.


>
> 2. On WinXP, using pgAdmin 3 1.0.0 and connecting to Cygwin pgsql 
> 7.3.4, I get these message while connecting to the server: 


So it says in the pgAdmin3 FAQ...
You may complain on pgsql-interfaces about this.

Regards,
Andreas




Re: Two bugs in pgAdmin3 1.0.0

From
"Dave Page"
Date:

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 06 October 2003 12:40
> To: Christopher Kings-Lynne
> Cc: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Two bugs in pgAdmin3 1.0.0
>
>
> Christopher Kings-Lynne wrote:
>
> > 1. When you change the statistics target of a column, eg:
> >
> > ALTER TABLE foo ALTER COLUMN bar SET STATISTICS 1000;
> >
> > It is not reflected in the 'code view' for the column object.
>
>
> We don't have statistics as property at the moment, do we need this?
> If so, that's a TODO item.

I've seen worse ideas to include as todo items.

I'll add it.

Regards, Dave.