Hi Team,
On Sat, Sep 24, 2016 at 3:23 AM, Ashesh Vashi <ashesh.va...@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.enterprisedb.com/> *http://www.linkedin.com/in/asheshvashi* <http://www.linkedin.com/in/asheshvashi> > > -- > > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise PostgreSQL Company > <http://www.enterprisedb.com> > > > *http://www.linkedin.com/in/asheshvashi* > <http://www.linkedin.com/in/asheshvashi> >
RM1735_part2.patch
Description: Binary data
-- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
