Re: PATCH: EXTENSION keyword not supported by pgAdmin3
От | Ashesh Vashi |
---|---|
Тема | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |
Дата | |
Msg-id | CAG7mmozWS=hH_-QoAo2T_emJMdzEAfQXznt_GdNDGcrWgh6t9g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: PATCH: EXTENSION keyword not supported by pgAdmin3
|
Список | pgadmin-hackers |
Aren't they installed in that schema?
--

--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:
On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:Hi,Something's not quite right - it's showing my table under an extension node!
On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.Yeah - that was a typical "Copy/Paste" error.PFA - the updated patch.Slightly better. Now the extension comments are shown under the public schema.--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: