Re: PATCH: RM#1735 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: PATCH: RM#1735
Date
Msg-id CA+OCxozqTcPp7z9tppWLzbZD=_QvjwDHCAkR=pRevq1kG_7yKg@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: RM#1735  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
List pgadmin-hackers
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

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: PATCH: RM#1735
Next
From: Ashesh Vashi
Date:
Subject: Re: PATCH: pgAgent support