Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1boS13-0003e0-22 for pgadmin-hackers@arkaria.postgresql.org; Mon, 26 Sep 2016 09:16:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1boS12-00081Z-LC for pgadmin-hackers@arkaria.postgresql.org; Mon, 26 Sep 2016 09:16:00 +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_2) (envelope-from ) id 1boS12-00081T-9Q for pgadmin-hackers@postgresql.org; Mon, 26 Sep 2016 09:16:00 +0000 Received: from mail-it0-x231.google.com ([2607:f8b0:4001:c0b::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1boS0v-0002jK-4j for pgadmin-hackers@postgresql.org; Mon, 26 Sep 2016 09:15:59 +0000 Received: by mail-it0-x231.google.com with SMTP id r192so68028193ita.0 for ; Mon, 26 Sep 2016 02:15:52 -0700 (PDT) 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=FREeuH4t0KZostj6Hl+h0HsdI8SJUnQ6UlXvYgOs86k=; b=h+ARAN/1EyBJ8kZDwEoxFtzZ3TPyQGbpWyVKwfvXKch2VOLMQLQOaCCQSPxq7GcvAZ D5mscunjN2TvvsNFbhEYI2KOp28wUrxifAlPJG1kCW+MNyt3M9UFw/IupfcH3n7SPss+ jzlOAcm/EsmqThyrNYVE+7lHH0I7jPmx8/nNLmE5OnIThn2yXEupoIBkvJfw18bpDLEu lFP1qbJ2S1dNVzzLmBnmn0krSQTkikX4fgBmvRVRa0kItCRyK3z0vXZPkiplBx2XdWET ddJ90BbOp2Ga6jGQroxOF5C8ESS/SvuWNZ0jVKSnaJ51iqg5rQT90/oyxeIkTzvc9Xtt IT0A== 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:from:date :message-id:subject:to:cc; bh=FREeuH4t0KZostj6Hl+h0HsdI8SJUnQ6UlXvYgOs86k=; b=JOsU2zG6lYbwPNM6TYzqPfiHO34YGNvyyBZY6DnStkEVX7MQDsGujvsoYHQlneA8YJ iF6yRxdq0qG/NVyqgvFDPQs4uggvoPH+eGUpaFw6Tk7hry+UvaYSoX8Pu0hVMtkDTJWj oTQY3xjMSkgNFihbbPBMQOdaVF0cXyc3XpgI4DQ5gyF7354OyQ/4XM8SBY3NqKDp/HlA KCW0skA/Zh3igpw1XEyUYxMZJL4mIs4EDGHpj/v+fZ0RpwqBmS5fnP8jng0MsSEM0SDj Er5ZXy0DcyiqqUh0IaoHImwOUerwIfAb6JoZQK5mCTup/U+qxag3QXqtyQzQtV11yAEC +KUw== X-Gm-Message-State: AA6/9RmZkwsW/kG+DrCSXKXBiUFNbpDJjYXkHYQoYng0ytinnU6UG0PRVF031PCSa8jUwY5JwBsyCBcFAMSBqA== X-Received: by 10.36.236.69 with SMTP id g66mr16466642ith.32.1474881351213; Mon, 26 Sep 2016 02:15:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.1.203 with HTTP; Mon, 26 Sep 2016 02:15:49 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Mon, 26 Sep 2016 10:15:49 +0100 Message-ID: Subject: Re: PATCH: RM#1735 To: Ashesh Vashi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary=94eb2c1170d206931b053d659320 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 --94eb2c1170d206931b053d659320 Content-Type: text/plain; charset=UTF-8 Thanks, applied. On Sat, Sep 24, 2016 at 12:04 AM, Ashesh Vashi < ashesh.vashi@enterprisedb.com> wrote: > Hi Team, > > > On Sat, Sep 24, 2016 at 3:23 AM, Ashesh Vashi < > ashesh.vashi@enterprisedb.com> wrote: > >> Hi Dave/Team, >> >> I've fixed the issue "No default schema when creating some schema >> objects". >> >> For package, allowing to change the schema at the create time only, as >> the logic required to change schema of an existing package required a lot >> of changes. And, I am reluctant to do it at this phase of the project. >> > I also find out that - when we refresh the schema node, it was returning > an array of node data instead of an individual node data. > > Please find the fix for it as part # 2. > > NOTE: First patch is still applicable. > > -- > > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise PostgreSQL Company > > > > *http://www.linkedin.com/in/asheshvashi* > > >> >> -- >> >> Thanks & Regards, >> >> Ashesh Vashi >> EnterpriseDB INDIA: Enterprise PostgreSQL Company >> >> >> >> *http://www.linkedin.com/in/asheshvashi* >> >> > > > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --94eb2c1170d206931b053d659320 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, applied.

On Sat, Sep 24, 2016 at 12:04 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Hi Team,


On Sat, Sep 24, 2016 at 3:23 AM, Ashesh Vashi <= ashesh.v= ashi@enterprisedb.com> wrote:
Hi Dave/Team,

I've fixed the issue "No default schema when creating some schem= a objects".

For package, allowing to change t= he schema at the create time only, as the logic required to change schema o= f an existing package required a lot of changes. And, I am reluctant to do = it at this phase of the project.
I also= find out that - when we refresh the schema node, it was returning an array= of node data instead of an individual node data.

= Please find the fix for it as part # 2.

NOTE: Firs= t patch is still applicable.

--

Thanks & Regards,
Ashesh Vash= i
E= nterpriseDB INDIA:=C2=A0Enterprise PostgreSQL Company


<= /span>

=C2=A0http://www.linkedin.com/in/asheshvashi=


<= div style=3D"margin:0pt 0pt 8px">

--

Thanks & Regards,

Ashes= h Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company


http://www.linkedin.com/in/asheshvashi




--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-ha= ckers




--
--94eb2c1170d206931b053d659320--