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
