Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etbwa-0007Zw-Kt for pgadmin-hackers@arkaria.postgresql.org; Wed, 07 Mar 2018 16:29:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etbwZ-0008LG-JK for pgadmin-hackers@arkaria.postgresql.org; Wed, 07 Mar 2018 16:29:31 +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.89) (envelope-from ) id 1etbwZ-0008L6-Dm for pgadmin-hackers@lists.postgresql.org; Wed, 07 Mar 2018 16:29:31 +0000 Received: from mail-wm0-x241.google.com ([2a00:1450:400c:c09::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1etbwV-0003y5-Hb for pgadmin-hackers@postgresql.org; Wed, 07 Mar 2018 16:29:30 +0000 Received: by mail-wm0-x241.google.com with SMTP id 139so5880414wmn.2 for ; Wed, 07 Mar 2018 08:29:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xrdq3M+DX7CxhFGL9GQ8PiOp+IqkJu6MIA1czfSEWnA=; b=YMQY976NrjeiNk9j2b4Iz5T8RmWCAG2rotaRlzKpbF550em+2rTtlgV/5caO11Vajd LM7t7Gm6qwcy8do1WsKJAOsWWT6Q/T4WL/txBC4aZG4kgPlMfu6AeTjhS5L1y02v142B AZpq5ABicnnpoPbAEeS+qRd1Sye/rgf3eRAVMdMmtujxlbyEWoyl/Cl+6PMarU8yaLV7 MchLh53AdfIvUqN2T/F0eVztBr6b5hLAckvU4FbMVCZPr6oCx2zAGpSRm7TNpjOak5jD dvRpY1SrN6Bmsbp4NWbBoyznLIvB4NK/FdoR2yySqgTQnC+tNHl8GVyHvSqXQ+0PyOb0 OLpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xrdq3M+DX7CxhFGL9GQ8PiOp+IqkJu6MIA1czfSEWnA=; b=CwJqYUWMTXLAV+V8MLP7k0CKsjpZNPleecMk0ZVDn9tKp5SUq+O1KcnPWJF8f1yzrW dhQAGd3augSWUMkEAfO5mURwxZqyQMJbV9bjyt3JYZULRoLgBbwNS01DSrhGVCuIY11C SYSduwJthVtfM8x/vB0SrLJGZf8+26M7diK/fLupO6wsk8kG/vuhgPGRd9cVelqemUjp WjRsl1q04Vyp1upZgb+j/DpcMETuC9+/cpwtsopEQLc/XTvnmX9Pu1+oWTb1yCLCMxGB uKMRYEYzHEP+UJHAp5RbnEE5gHTqgD9HKBIBx7shozKiEEOoadqxumldW/u1U8aLtMyx PDDg== X-Gm-Message-State: AElRT7GCAPqMRLpACbNsKvTzYtUaTJ+vCOIt+AGC3PLNkkvBOBFRRQwG zVAPsQEG6iURSMPyZQVRsxyPsdUj9SuqKa2ijXlRqQ== X-Google-Smtp-Source: AG47ELsjl0W0BjLht9gEnUMRYr50R2ayYfR7NsSMIeMVnUv5PUpXVLPYb45+tr6JURTHB8kmcu/8ErRYFLSeo50mX9k= X-Received: by 10.28.167.151 with SMTP id q145mr16143814wme.64.1520440166426; Wed, 07 Mar 2018 08:29:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.109.7 with HTTP; Wed, 7 Mar 2018 08:29:25 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Wed, 7 Mar 2018 16:29:25 +0000 Message-ID: Subject: Re: [pgAdmin4][RM#2989] To fix the issue in Table node To: Murtuza Zabuawala Cc: Joao De Almeida Pereira , pgadmin-hackers Content-Type: multipart/alternative; boundary="001a114b3cd405c3eb0566d510bd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a114b3cd405c3eb0566d510bd Content-Type: text/plain; charset="UTF-8" Hi On Wed, Mar 7, 2018 at 2:59 PM, Murtuza Zabuawala < murtuza.zabuawala@enterprisedb.com> wrote: > Hi Dave, > > PFA updated patch. > > Using your example on the ticket, I added a "character varying (32)" column with NOT NULL to the table. When I then edit the column, and turn off NOT NULL (making no other changes), the SQL generated is: ALTER TABLE public.test_drop ALTER COLUMN col2 TYPE character varying (32) COLLATE pg_catalog."default"; ALTER TABLE public.test_drop ALTER COLUMN col2 DROP NOT NULL; I didn't see that when turning off NOT NULL for col1. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a114b3cd405c3eb0566d510bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Wed, Mar 7, 2018 at 2:59 PM, Murtuza Zabuawala &= lt;= murtuza.zabuawala@enterprisedb.com> wrote:
Hi Dave,

PFA updated patch.


U= sing your example on the ticket, I added a "character varying (32)&quo= t; column with NOT NULL to the table. When I then edit the column, and turn= off NOT NULL (making no other changes), the SQL generated is:
ALTER TABLE public.test_drop
=C2=A0 =C2=A0 ALTE= R COLUMN col2 TYPE character varying (32) COLLATE pg_catalog."default&= quot;;
ALTER TABLE public.test_drop
=C2=A0 =C2=A0 ALTER= COLUMN col2 DROP NOT NULL;

I didn't see= that when turning off NOT NULL for col1.

--
=
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter= : @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgre= SQL Company
--001a114b3cd405c3eb0566d510bd--