Postgres Pro
Downloads
Home   >   mailing lists

Observed bug in pgAdmin3 - Mailing list pgadmin-hackers

From Murtuza Zabuawala
Subject Observed bug in pgAdmin3
Date
Msg-id 568A17FD.5030204@enterprisedb.com
Whole thread Raw
Responses Re: Observed bug in pgAdmin3  (Neel Patel <neel.patel@enterprisedb.com>)
List pgadmin-hackers
Tree view
Hi All,

I observed an issue while creating new collation (in schemas).

Steps to reproduce,
1) Connect to postgres database
2) Expand 'postgres' database
3) Expand 'schemas'
4) Expand 'Collations'
5) Right click & Click "New Collation..."

Provide > Properties:
  Name: test-11
  Owner: postgres
  Schema: pg_toast

Provide > Definition:
  Copy collation: pg_catalog."en_IN.utf8"

6)
Now click on SQL tab and you will see the wrong sql created, schema name is appended twice in alter statement.

CREATE COLLATION pg_toast."test-11" FROM pg_catalog."en_IN.utf8";
ALTER COLLATION pg_toast."pg_toast.""test-11"""
  OWNER TO postgres; 


Let me know for more information.

Regards,
Murtuza Zabuawala

pgadmin-hackers by date:

Previous
From: Ashesh Vashi
Date:
Subject: pgAdmin 4 commit: Set options fetched from the server as it is only whe
Next
From: Ashesh Vashi
Date:
Subject: pgAdmin 4 commit: Allow to use the url with/without the node id in the