Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aFz8t-0003Lj-W1 for pgadmin-hackers@arkaria.postgresql.org; Mon, 04 Jan 2016 07:01:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aFz8t-00074k-Ct for pgadmin-hackers@arkaria.postgresql.org; Mon, 04 Jan 2016 07:01:23 +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 1aFz8s-00074d-SC for pgadmin-hackers@postgresql.org; Mon, 04 Jan 2016 07:01:22 +0000 Received: from mail-pf0-x22f.google.com ([2607:f8b0:400e:c00::22f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aFz8l-0006zx-J4 for pgadmin-hackers@postgresql.org; Mon, 04 Jan 2016 07:01:22 +0000 Received: by mail-pf0-x22f.google.com with SMTP id e65so144755980pfe.1 for ; Sun, 03 Jan 2016 23:01:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-type; bh=WGj6QgW0T9MtWDnc/V5P/D5ZTwini7BRSB/NukNdgSQ=; b=VwPjRyiA2IjFTQikppvSzkRG4owA5o554aDumooUJyQQ1R2QPVIZ8+23Hu4MY/uIi+ Ks9HiHPD5A3RG+rIRoExra7MJ7oXUPeNZeqpKDgM+x7t654IwIoGgaogR7wQTpV8sEIV seLNlJYb+Lgt1ux7wgYQlWllf8xAVCu8BHjAy7e5BdkaGgrrhvMyJweWjgDu5OLCGHq0 SxUgFeiTE8sd1GqpGfU6A62Y6i6AMY1yQSaAY+oSpoUB8AorMLo5aMNJlKBGO84rkIyd xPkDlcoAj9KjKJxhW7gvs4a9fCNp2xrFPDLkPfqJ9XMTc0FmGQoC4b4KRTEREPNDRopx mXyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-type; bh=WGj6QgW0T9MtWDnc/V5P/D5ZTwini7BRSB/NukNdgSQ=; b=DVTN8VfjSJ9Axoiqq1tEihV1zJo3mo2qZ8nDTvcoMgvIu5i7inLcoO4V4OXib/VTGb zBnwLlI3nxGfhhNwtdjyVvrp5LZUGjkRE/Vlwcyu4I1f+xMnPE3CH+r7IgpP9Sr1i1XO 0qlUzCsojbfJtLV4SELD3tnMhSznlY/znSk0hWHvwOyxOKHTa/YAhn8YbxKR2d8y2ryW iXb+yQ//BUXbgOTFpu2oAjWbBnWhyh1yhFFmf2TBlxferb12mRtESqMmb64Gv3ayjlv2 jbknMr0hlJjHynLlV3CmhDlQ+szaB83v1EjJTKbBR14PWvREu1WwZOV/7tV2tAJtKjbS ZZTA== X-Gm-Message-State: ALoCoQmmonGMlEeaZaqPlMfsQvp2GQncEq7kMhpG780QYbjijYcKyzbleguWxA0qnTAczCKNBIaWbg4xBf3c5/F6kwcpAfMfPbU7ZscrJEREaSDacMCPfla1d74VT6yVOlSCCudWqX+40IsUMcPSFpUN7Zm7dStXsAjlpaALJm4LRG19yyax1DH5PdqxZz+fN59Y65H4yN2HlgOrmrLuZS9bIqCqpUIAMw== X-Received: by 10.98.65.219 with SMTP id g88mr109833297pfd.63.1451890873032; Sun, 03 Jan 2016 23:01:13 -0800 (PST) Received: from [172.24.35.244] ([59.162.78.200]) by smtp.gmail.com with ESMTPSA id y26sm51633004pfi.89.2016.01.03.23.01.11 for (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jan 2016 23:01:12 -0800 (PST) To: pgadmin-hackers@postgresql.org From: Murtuza Zabuawala Subject: Observed bug in pgAdmin3 Message-ID: <568A17FD.5030204@enterprisedb.com> Date: Mon, 4 Jan 2016 12:28:05 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------060104030106020802070609" 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 This is a multi-part message in MIME format. --------------060104030106020802070609 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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 --------------060104030106020802070609 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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

--------------060104030106020802070609--