Re: PATCH: RM#1735

Поиск
Список
Период
Сортировка
От Ashesh Vashi
Тема Re: PATCH: RM#1735
Дата
Msg-id CAG7mmow1dHq5TZfnOJhj21hE-KdFi2O2XYh=aJBn4KRHmfZ21g@mail.gmail.com
обсуждение исходный текст
Ответ на PATCH: RM#1735  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Ответы Re: PATCH: RM#1735
Список pgadmin-hackers
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


Вложения

В списке pgadmin-hackers по дате отправления:

Предыдущее
От: Ashesh Vashi
Дата:
Сообщение: PATCH: RM#1733
Следующее
От: Ashesh Vashi
Дата:
Сообщение: pgAdmin 4 commit: Fixes#1737 - Setting the schedma-id as the pid (paren