From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |
Date: | 2011-12-01 13:22:52 |
Message-ID: | CA+OCxoyyN4dLC84h7erj7QeXCCyzHbMGFQs+CDDGc19oeSxanA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com
> wrote:
> 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.
>
>
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 | Content-Type | Size |
---|---|---|
Screen Shot 2011-12-01 at 13.21.15.png | image/png | 78.9 KB |
9.1.backup | application/octet-stream | 16.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2011-12-01 13:23:57 | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |
Previous Message | Ashesh Vashi | 2011-12-01 12:57:15 | Re: PATCH: EXTENSION keyword not supported by pgAdmin3 |