Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aNL0v-0007hF-62 for pgadmin-hackers@arkaria.postgresql.org; Sun, 24 Jan 2016 13:47:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aNL0u-00087d-NX for pgadmin-hackers@arkaria.postgresql.org; Sun, 24 Jan 2016 13:47:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aNL0u-00087X-9R for pgadmin-hackers@postgresql.org; Sun, 24 Jan 2016 13:47:32 +0000 Received: from mail-yk0-x22e.google.com ([2607:f8b0:4002:c07::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aNL0q-0005f4-SE for pgadmin-hackers@postgresql.org; Sun, 24 Jan 2016 13:47:31 +0000 Received: by mail-yk0-x22e.google.com with SMTP id k129so136039035yke.0 for ; Sun, 24 Jan 2016 05:47:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RIqLD4lyuZctMAiDyZ2Dl6Li4RFAU+Crz/6imhE++DI=; b=MyAoGKqVn7x1TbE3T9/X0iW103f0u8CQdRooUcqYxe38lb2MJuSH6BM9PuJUhDEc1W REopswEf91wSYdaQbIEaVcdp40Z9idfV0DypU4x7YXaO7A3YAWp1XxGhrYy9vyP7413X jl+rdRrX5dsm7hF6C93K2dMAM/5afRmV0BIGhN9PVr2Po3QQd3Z02R9av05Hg9rUo+u6 MMlst4DRm3R2gpRH2m9r07bknZ8htjXD5QZLg/w5cbWyAkq0iQrJ/ouu4T5p2jwlt1IU xvnWiHsfwrQ8Gi6zEdKd2cGF2HFfrZXT9Pewz4VG+1a5WcqOFObvUBPDhAHy8SbTGlLm heAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=RIqLD4lyuZctMAiDyZ2Dl6Li4RFAU+Crz/6imhE++DI=; b=FGFiM1Cy03NCXwG61INGl7JsovlwYGSHgdP4p740/anQf9PgTdud52Impbj3Qz3uoy NHd8lUFaInf8mdtQ81njSa0Vm0WfguwCbQfyryV+3rX2pMzu46c+dL8ByxiNjoB1m+/j rqbLM3N6Cb8yaplkUWUhdYibqFc4izAqPuquWjsNp4r8gh+oyK0PRfdGP29cnnBy5GYH /K23Fr8vP30RABhZyfEudYqir5Mn1xYhJmGKIUscRxW7shxIYUKEyQGAWOg76iA0CQFi rBfYdPzXG0HCHfRRQozjCd+QBqPZ3v63HcMdoaE4jXa09qBw3aTVuWB6ApnSTN2yUDTy ao3Q== X-Gm-Message-State: AG10YORkZ1FeWbuQULzKppiNX0jacOLr2sU1FIilF6e91vudLiaOofVaCl/8jgdpKpkO7kYz5NPJHobkRZD3mqvZ MIME-Version: 1.0 X-Received: by 10.37.64.134 with SMTP id n128mr6167991yba.51.1453643246343; Sun, 24 Jan 2016 05:47:26 -0800 (PST) Received: by 10.37.202.75 with HTTP; Sun, 24 Jan 2016 05:47:26 -0800 (PST) In-Reply-To: <568A17FD.5030204@enterprisedb.com> References: <568A17FD.5030204@enterprisedb.com> Date: Sun, 24 Jan 2016 19:17:26 +0530 Message-ID: Subject: Re: Observed bug in pgAdmin3 From: Neel Patel To: Murtuza Zabuawala Cc: pgadmin-hackers Content-Type: multipart/mixed; boundary=001a11c0158e54b70b052a14b1af X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a11c0158e54b70b052a14b1af Content-Type: multipart/alternative; boundary=001a11c0158e54b703052a14b1ad --001a11c0158e54b703052a14b1ad Content-Type: text/plain; charset=UTF-8 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 > > --001a11c0158e54b703052a14b1ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

We have fixed the issue as mentione= d below.

Issue :-
When we create = any collation then two times schema name was appended to query.
<= br>
Fix:-
With this fix, schema name will append= ed 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 Pat= el

On = Mon, Jan 4, 2016 at 12:28 PM, Murtuza Zabuawala <murtuza.= zabuawala@enterprisedb.com> wrote:
=20=20 =20=20=20=20 =20=20
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:
=C2=A0 Name: test-11
=C2=A0 Owner: postgres
=C2=A0 Schema: pg_toast

Provide > Definition:
=C2=A0 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"&qu= ot;"
=C2=A0 OWNER TO postgres;=C2=A0


Let me know for more information.

Regards,
Murtuza Zabuawala


--001a11c0158e54b703052a14b1ad-- --001a11c0158e54b70b052a14b1af Content-Type: application/octet-stream; name="collation_fix.patch" Content-Disposition: attachment; filename="collation_fix.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_ijslkyou0 ZGlmZiAtLWdpdCBhL3BnYWRtaW4vZGxnL2RsZ0NvbGxhdGlvbi5jcHAgYi9w Z2FkbWluL2RsZy9kbGdDb2xsYXRpb24uY3BwCmluZGV4IDQ3YWQzYzcuLjQz MmVmZGYgMTAwNjQ0Ci0tLSBhL3BnYWRtaW4vZGxnL2RsZ0NvbGxhdGlvbi5j cHAKKysrIGIvcGdhZG1pbi9kbGcvZGxnQ29sbGF0aW9uLmNwcApAQCAtMTc4 LDcgKzE3OCw3IEBAIHd4U3RyaW5nIGRsZ0NvbGxhdGlvbjo6R2V0U3FsKCkK IAkJfQogCQlzcWwgKz0gd3hUKCI7XG4iKTsKIAotCQlBcHBlbmRPd25lck5l dyhzcWwsIHd4VCgiQ09MTEFUSU9OICIpICsgc2NoZW1hLT5HZXRRdW90ZWRQ cmVmaXgoKSArIHF0SWRlbnQobmFtZSkpOworCQlBcHBlbmRPd25lck5ldyhz cWwsIHd4VCgiQ09MTEFUSU9OICIpICsgbmFtZSk7CiAJfQogCUFwcGVuZENv bW1lbnQoc3FsLCB3eFQoIkNPTExBVElPTiAiKSArIHF0SWRlbnQoY2JTY2hl bWEtPkdldFZhbHVlKCkpICsgd3hUKCIuIikgKyBxdElkZW50KEdldE5hbWUo KSksIGNvbGxhdGlvbik7CiAK --001a11c0158e54b70b052a14b1af Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers --001a11c0158e54b70b052a14b1af--