Re: PATCH: EXTENSION keyword not supported by pgAdmin3 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: PATCH: EXTENSION keyword not supported by pgAdmin3
Date
Msg-id CA+OCxoyyN4dLC84h7erj7QeXCCyzHbMGFQs+CDDGc19oeSxanA@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: EXTENSION keyword not supported by pgAdmin3  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Responses Re: PATCH: EXTENSION keyword not supported by pgAdmin3
List pgadmin-hackers


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,

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.

Something's not quite right - it's showing my table under an extension node!

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

Attachment

pgadmin-hackers by date:

Previous
From: Ashesh Vashi
Date:
Subject: Re: PATCH: EXTENSION keyword not supported by pgAdmin3
Next
From: Ashesh Vashi
Date:
Subject: Re: PATCH: EXTENSION keyword not supported by pgAdmin3