Dave Page wrote:
-Original Message-
From: Dave Page
Sent: 06 October 2003 10:17
To: Matej Rizman; [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] PgAdmin III: Two bugs
Hi Matej
-Original Message-
From: Matej Rizman [mailto:[EMAIL PROTECTED]
Sent: 05 October 2003 23:37
T
LeavesThe problem I was having with ssh tunneling was resolved by making the
following change to the port
forward scenario:
pg_hba.conf:
#TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
local all all
trust
hostall
> -Original Message-
> From: Dave Page
> Sent: 06 October 2003 10:17
> To: Matej Rizman; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] PgAdmin III: Two bugs
>
>
> Hi Matej
>
> > -Original Message-
> > From: Matej Rizman [mailto:[EMAIL PROTECTED]
> > Sent: 05 October 2003
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 06 October 2003 12:40
> To: Christopher Kings-Lynne
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Two bugs in pgAdmin3 1.0.0
>
>
> Christopher Kings-Lynne wrote:
>
> > 1. When you change the statis
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 TOD
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 serv
Hi Matej
> -Original Message-
> From: Matej Rizman [mailto:[EMAIL PROTECTED]
> Sent: 05 October 2003 23:37
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] PgAdmin III: Two bugs
>
>
>
> PgAdmin III version: 1.0.0
>
> First bug:
> Creating UNIQUE constraint executes ALTER TABLE ...
PgAdmin III version: 1.0.0
First bug:
Creating UNIQUE constraint executes ALTER TABLE ... ADD CONSTRAINT asfd
PRIMARY KEY
Second bug:
This bug has already been reported, but until now I haven't been able to
consistently reproduce it... Well, there is scenario that causes this bug to
show up
