From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Harshal Dhumal <harshal(dot)dhumal(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Control for selecting multiple columns [pgadmin4] |
Date: | 2016-03-17 17:03:05 |
Message-ID: | CA+OCxow9fzeSSHjs+m4VFNcJMb7+Ka5g1mbPx-tnZDK7S1ypGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
I tried that, but get the attached error when testing. I'm on a clean tree,
with the WIP tables patch (which, by the way, doesn't look much like Arun's
design so is likely to need a lot of layout work). I've restarted,
refreshed etc.
[image: Inline image 1]
On Thu, Mar 17, 2016 at 6:04 AM, Harshal Dhumal <
harshal(dot)dhumal(at)enterprisedb(dot)com> wrote:
> Hi Dave,
>
> I have used same control in primary key constraint for selecting multiple
> columns. So to test this control please extract attached table.zip file
> under schema node. This zip contains table, column and constraint node with
> primary key support (as constraint node has dependency on table and column
> node). Also you will need to apply multiselect control patch separately as
> this zip does not contain the same.
>
>
> Thank you,
>
> Harshal
>
>
> --
> *Harshal Dhumal*
> *Software Engineer *
>
>
>
> EenterpriseDB <http://www.enterprisedb.com>
>
> On Tue, Mar 15, 2016 at 10:13 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> It seems to be missing the test dialogue?
>>
>> On Tue, Mar 15, 2016 at 8:47 AM, Harshal Dhumal <
>> harshal(dot)dhumal(at)enterprisedb(dot)com> wrote:
>>
>>> Hi,
>>>
>>> PFA generalized updated patch for backform multiSelectControl.
>>>
>>> --
>>> *Harshal Dhumal*
>>> *Software Engineer *
>>>
>>>
>>>
>>> EenterpriseDB <http://www.enterprisedb.com>
>>>
>>> On Tue, Mar 8, 2016 at 1:04 PM, Harshal Dhumal <
>>> harshal(dot)dhumal(at)enterprisedb(dot)com> wrote:
>>>
>>>> Hi,
>>>>
>>>> PFA backform control for selecting multiple columns.(This control
>>>> depends on column node.)
>>>>
>>>> Usage:
>>>>
>>>> {
>>>> id: 'columns', label: '{{ _('Columns') }}',
>>>> type: 'collection', group: '{{ _('Definition') }}', editable:true,
>>>> canDelete: true, canAdd: true, control: Backform.MultiColumnSelectControl,
>>>> deps: ['index'], node: 'column',
>>>> model: pgBrowser.Node.Model.extend({
>>>> keys: ['column'],
>>>> defaults: {
>>>> column: undefined
>>>> }
>>>> })
>>>> }
>>>>
>>>>
>>>> Note: When using this control model should have *column* attribute.
>>>> And node property should be *column*.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Harshal Dhumal*
>>>> *Software Engineer *
>>>>
>>>>
>>>>
>>>> EenterpriseDB <http://www.enterprisedb.com>
>>>>
>>>
>>>
>>>
>>> --
>>> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgadmin-hackers
>>>
>>>
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2016-03-17 17:20:51 | pgAdmin 4 commit: Log exceptions raised under the servers module. |
Previous Message | Harshal Dhumal | 2016-03-17 15:04:29 | Re: Subnode grid row close issue [pgAdmin4] |