Observed bug in pgAdmin3

From: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: Observed bug in pgAdmin3
Date: 2016-01-04 06:58:05
Message-ID: 568A17FD.5030204@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

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

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Ashesh Vashi 2016-01-04 07:13:46 pgAdmin 4 commit: Allow to use the url with/without the node id in the
Previous Message Ashesh Vashi 2016-01-04 06:49:09 pgAdmin 4 commit: Set options fetched from the server as it is only whe