Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aL7bY-00032o-Gd for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Jan 2016 11:04:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aL7bX-0003un-Iu for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Jan 2016 11:04:11 +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 1aL7bX-0003ub-3R for pgadmin-hackers@postgresql.org; Mon, 18 Jan 2016 11:04:11 +0000 Received: from mail-wm0-x233.google.com ([2a00:1450:400c:c09::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aL7bT-0005T4-HP for pgadmin-hackers@postgresql.org; Mon, 18 Jan 2016 11:04:10 +0000 Received: by mail-wm0-x233.google.com with SMTP id 123so47441600wmz.0 for ; Mon, 18 Jan 2016 03:04:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:content-type; bh=FTde4LwW0Lb0/NZGigokXb/r9f68FSgISQbcZQB//9g=; b=RwlnvZtziO9YLssOJSb+/APRiQrMWvSMvbZzRjVVxXrSNqE0p8MQon/bnd0p8RB1dS GNpIOmIXVAvtoRE//iNbdiEEq/ZrIehdagTGUR0sC+1391vm2IZBI69etpHgr14Wn2+d hcxl871nbRXcNlCMzzEpN+ignOr+vdPpXWYePacRQw1gLOsFGbukiAsZtr8Be26ZHS70 o2KDt8teZCAKjY6WUtNPROMaErnj1zUEsZKFAILNT8m/3gqJaRU6hQ/3S4Xz6rByObUl 9op0sSs5bZ23sEANG8otaTZmG9Qe8EPb6v/AmtM35QUvR48TxL6f3WDC/cPo9/e3AYtX KvzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=FTde4LwW0Lb0/NZGigokXb/r9f68FSgISQbcZQB//9g=; b=iKRAasi+mQrudS3pGXQYsDQE2YfplH3C1HV2vUGfXjDEVpsZLEdLpdzicRpl/ZhaHf KEA6IoaDfFApK5w2+jw++fiVKkL67xbpUcn+BfMnhgAVw8RPszIFDbmVKfthOL3qG3Dp 2hFCDYwfjR6VVNgcFWHr7ldEjORTbmOX96w+06wmTjVQdStwbHnsQnrtw8SbQ3XhDWHs 7+aNboW1nEHwUx941uQLgpVSX+zegHO8vrroHNY4XyEuIoLwHwdfcM6lS999LOz4YC50 vNn57KPZLEOKv0AWfjJdzKG6uhmZjiTQ8FDiD1yDDaugoOxkDZphBHEAROoVBrc7jpTh Xc8w== X-Gm-Message-State: ALoCoQm8c+U88Ku3iEUexpmbNxiojgq5rwp/MtMl+ZEH0wJly0kQvTc0cBofSJtSbolCQygd3mbSDV5qrZKwL3siIcxJHtj3YUGcStmXkO6F/iUVKMANoPA= X-Received: by 10.194.203.99 with SMTP id kp3mr23782520wjc.3.1453115045870; Mon, 18 Jan 2016 03:04:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.15.66 with HTTP; Mon, 18 Jan 2016 03:03:36 -0800 (PST) From: Surinder Kumar Date: Mon, 18 Jan 2016 16:33:36 +0530 Message-ID: Subject: [pgAdmin3][Extension]: Wrong SQL generated To: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary=047d7bd91af22092c1052999b6e1 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 --047d7bd91af22092c1052999b6e1 Content-Type: text/plain; charset=UTF-8 Hi all, While implementing Extension module in pgAdmin4, I came to know that there is an bug in pgadmin3. Following are the steps to reproduce it: 1. Edit an existing extension. 2. In definition tab, set schema and version fields to empty. 3. In SQL tab, it generates an sql for the changes made which is wrong, it shouldn't generate sql for the schema and version field if it is kept empty, both fields should be validated. Below is the wrong SQL generated: *ALTER EXTENSION btree_gin* * SET SCHEMA ;* *ALTER EXTENSION btree_gin* * UPDATE TO ;* Let me know for any comments. Thanks Surinder Kumar --047d7bd91af22092c1052999b6e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,


While implementing Ext= ension module in pgAdmin4, I came to know that there is an bug in pgadmin3.=

Following are the steps to reproduce it:
1. Edit an existing extension.
2. In definition tab, set schema= and version fields to empty.
3. In SQL tab, it generates an sql = for the changes made which is wrong, it shouldn't generate sql for the = schema and version field if it is kept empty, both fields should be validat= ed.


Below is the wrong SQL generate= d:

ALTER EXTENSION btree_gin
=C2=A0 SET SCHEMA ;
ALTER EXTENSION btree_gin
=C2=A0 UPDATE TO ;
<= b style=3D"background-color:rgb(255,255,255)">

Let me know for a= ny comments.

<= /b>
Thanks
Surinder Kumar
--047d7bd91af22092c1052999b6e1--