Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1boS0t-0003dc-88 for pgadmin-hackers@arkaria.postgresql.org; Mon, 26 Sep 2016 09:15:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1boS0s-00080h-R9 for pgadmin-hackers@arkaria.postgresql.org; Mon, 26 Sep 2016 09:15:50 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1boS0f-0007eP-6B for pgadmin-hackers@postgresql.org; Mon, 26 Sep 2016 09:15:37 +0000 Received: from mail-io0-x230.google.com ([2607:f8b0:4001:c06::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1boS0c-0004Mq-P8 for pgadmin-hackers@postgresql.org; Mon, 26 Sep 2016 09:15:36 +0000 Received: by mail-io0-x230.google.com with SMTP id r145so176025938ior.0 for ; Mon, 26 Sep 2016 02:15:34 -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=NZcKEcL2ICTjk4YA/XfvEAH5Ep5ZiZ4Xc2hUU5vK7rs=; b=m4Yhn3yvX1nngXdD8V2N/l2IGtTPNhbnC+O8qoz8POf8TV50omYItIpMKFTOWwCdv+ AznhGLHnfdQTJpombpQ61fUCPRsNAMOoUEWmgIwZx6nRio+fBRQiPe/8OEGFmX2gxQEL MfdihuEO/LtRAV7iwh3S2oMz5np+BbyuWeoCELDFVAYSpmcyW8Ixzjc1C36tz8QAEQRf Qrd3wc/yqy/ZsY/pRb1qoQqeJr8gWUtIBQhqSW2amKdmwZTqi92JJM/45/hk12COApCk 9y4c2NgdU8F8FZwKjBvNXpV8RjVZ6+ZjyRHB4rpN400bv7Axz+Ckow2Vpk0BmEFAWINC Z42Q== 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=NZcKEcL2ICTjk4YA/XfvEAH5Ep5ZiZ4Xc2hUU5vK7rs=; b=MHUHEr5fQ+q7LQVSK0Iujd9K/zp6x0CPpJ3kepAfVZnscxVyTsay4l/IyAY6AuGTOA wMe8C715jWiLWGnbsP/2eWJR9yOEuzNSP9x8c3NAC5t3lMl9kcpzUgP8sUftgRWIzENr Kwwp1bNuX4GpAXTTm/damZZGFlXwk4DqTz6Fe6Md5g96ilCfb2C7RWDA+ynWVee1cp6K 7RHTp8ADtaghQcFmeUo5MfRcVBhQVzekgcoXWCGEvTl+KoY82cJawaQbYQBJ7ufH4OB0 dd3aaSrHGKYmn2nBCeLPFXWME+QlKY34v6feOz9XhzkL92vZdFMjRs7KylstJEFXHmKZ hAPw== X-Gm-Message-State: AE9vXwOYUw5X+ELA8IVBH+9BKw+Gz+Kry0jWNQ6bjpFMsiWPMzMFTmZXVtDNibSl3Kea8sxVi5zRttExOYIsGw== X-Received: by 10.107.12.140 with SMTP id 12mr20666176iom.6.1474881334006; Mon, 26 Sep 2016 02:15:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.1.203 with HTTP; Mon, 26 Sep 2016 02:15:33 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Mon, 26 Sep 2016 10:15:33 +0100 Message-ID: Subject: Re: PATCH: RM#1735 To: Ashesh Vashi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary=001a113f8f1cffe91e053d65915a X-Pg-Spam-Score: -1.2 (-) 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 --001a113f8f1cffe91e053d65915a Content-Type: text/plain; charset=UTF-8 Thanks, applied. On Fri, Sep 23, 2016 at 10:53 PM, 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. > > -- > > 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 --001a113f8f1cffe91e053d65915a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, applied.

On Fri, Sep 23, 2016 at 10:53 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Hi Dave/Team,

I'= ve fixed the issue "No default schema when creating some schema object= s".

For package, allowing to change the schem= a at the create time only, as the logic required to change schema of an exi= sting package required a lot of changes. And, I am reluctant to do it at th= is phase of the project.

--

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-ha= ckers




--
--001a113f8f1cffe91e053d65915a--