[pgadmin-support] PgAdmin III: Two bugs
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: 1) add new connection to server and enter any database as initial database, 2) connect using this connection, 3) drop database that was entered as an initial database. PgAdmin III shows message that this database cannot be dropped and crashes. Regards, Matej Rizman ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-support] PgAdmin III: Two bugs
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 ... ADD > CONSTRAINT asfd PRIMARY KEY I cannot reproduce that - what steps did you take? > 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: > 1) add new connection to server and enter any database as > initial database, > 2) connect using this connection, > 3) drop database that was entered as an initial database. > > PgAdmin III shows message that this database cannot be > dropped and crashes. I fixed that one last week :-) Regards, Dave, ---(end of broadcast)--- TIP 8: explain analyze is your friend
[pgadmin-support] Two bugs in pgAdmin3 1.0.0
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 ---(end of broadcast)--- TIP 8: explain analyze is your friend
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. 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 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-support] Two bugs in pgAdmin3 1.0.0
> -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 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. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-support] PgAdmin III: Two bugs
> -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 > > To: [EMAIL PROTECTED] > > Subject: [pgadmin-support] PgAdmin III: Two bugs > > > > > > > > PgAdmin III version: 1.0.0 > > > > First bug: > > Creating UNIQUE constraint executes ALTER TABLE ... ADD > > CONSTRAINT asfd PRIMARY KEY > > I cannot reproduce that - what steps did you take? Scrub that, I see it. If you right click and then create New Unique Constraint then you get a primary key, however if you do it from the table properties dialgoue (as I do) it works fine apart from another bugette in which the anem is doubled (ie frog becomes frogfrog). Andreas; can you take a look at this please? I've spent a while on it but haven't figured it out and need to get on with some paid work (and you'll no doubt fix it in a few minutes :-))... Cheers, Dave. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[pgadmin-support] TUNNEL RESOLVED
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 all127.0.0.1 255.255.255.255 trust hostall all 172.16.1.0 255.255.255.0 trust <<<-Added -L8887:172.16.1.17:5432 <<<--Used the local private IP addres in the port forward argument. Without this I get the connection refused by host in the Putty log . Jim ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-support] PgAdmin III: Two bugs
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 To: [EMAIL PROTECTED] Subject: [pgadmin-support] PgAdmin III: Two bugs PgAdmin III version: 1.0.0 First bug: Creating UNIQUE constraint executes ALTER TABLE ... ADD CONSTRAINT asfd PRIMARY KEY I cannot reproduce that - what steps did you take? Scrub that, I see it. If you right click and then create New Unique Constraint then you get a primary key, however if you do it from the table properties dialgoue (as I do) it works fine apart from another bugette in which the anem is doubled (ie frog becomes frogfrog). Andreas; can you take a look at this please? I've spent a while on it but haven't figured it out and need to get on with some paid work (and you'll no doubt fix it in a few minutes :-))... Fixed in head and branch. dlgIndexConstraint::GetSql() was hard-coded to "PRIMARY KEY" instead of wxString(typeList[objectType].typeName).Upper(). Regards, Andreas ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
