Postgres Pro
Downloads
Home   >   mailing lists

Re: Observed bug in pgAdmin3 - Mailing list pgadmin-hackers

From Neel Patel
Subject Re: Observed bug in pgAdmin3
Date
Msg-id CACCA4P3L+C_Lvm5ri3oV2DXjiuEGsbMLeFgMVEfo4xZ55m3duw@mail.gmail.com
Whole thread Raw
In response to Observed bug in pgAdmin3  (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>)
List pgadmin-hackers
Tree view
Hi,

We have fixed the issue as mentioned below.

Issue :-
When we create any collation then two times schema name was appended to query.

Fix:-
With this fix, schema name will appended only one time and create query for collation will execute correctly.

Please find attached patch file. Review it and let us know for any comments.

Thanks,
Neel Patel

On Mon, Jan 4, 2016 at 12:28 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:
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


Attachment

pgadmin-hackers by date:

Previous
From: Timon
Date:
Subject: Re: 1.20.0 build error on Fedora 23
Next
From: Neel Patel
Date:
Subject: Re: [pgAdmin3][Extension]: Wrong SQL generated