From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Matej Rizman" <matej(dot)rizman(at)guest(dot)arnes(dot)si>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: PgAdmin III: Two bugs |
Date: | 2003-10-06 09:16:49 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B75C@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi Matej
> -----Original Message-----
> From: Matej Rizman [mailto:matej(dot)rizman(at)guest(dot)arnes(dot)si]
> Sent: 05 October 2003 23:37
> To: pgadmin-support(at)postgresql(dot)org
> 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,
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-10-06 11:01:38 | Two bugs in pgAdmin3 1.0.0 |
Previous Message | ljb | 2003-10-06 00:21:45 | Re: 7.4beta4: make check broken? |