From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |
Date: | 2011-12-01 12:57:15 |
Message-ID: | CAG7mmoyFebs_VUqNYVBPGAx6R=24Qudv2yZEYo6To7qqa0Ad6g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi,
>
> On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
> <ashesh(dot)vashi(at)enterprisedb(dot)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.
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com/>
*http://www.linkedin.com/in/asheshvashi*
>
> PFA.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Attachment | Content-Type | Size |
---|---|---|
FB20196_v2.patch | application/octet-stream | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-12-01 13:22:52 | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |
Previous Message | Dave Page | 2011-12-01 11:13:16 | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |