| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin4][Patch]: RM #3029 Cannot sort columns when importing data |
| Date: | 2018-10-31 10:10:23 |
| Message-ID: | CA+OCxozAS+zAUzzb10v4wG_9ZOj_yAOBNYAOQEkExwbNAeLK9A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Thanks, patch applied.
On Thu, Oct 25, 2018 at 11:58 AM Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
wrote:
> Hi Hackers,
>
> Attached is the patch to fix the RM #3029 Cannot sort columns when
> importing data.
> Select2 orders the selections based on the order of the `<options>` behind
> the scenes. This means that the order will typically match the order of the
> options as they appear in the dropdown. For *import/export* it shows in
> the order of columns define in the table.
>
> Solution: I have just reorders the options inside the select2 every time,
> an item is selected. I have made this change into the select2 control with
> new option "*preserveSelectionOrder*" by default it is false, so won't
> impact any other module.
>
> --
> *Akshay Joshi*
>
> *Sr. Software Architect *
>
>
>
> *Phone: +91 20-3058-9517Mobile: +91 976-788-8246*
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2018-10-31 10:30:41 | pgAdmin 4 commit: Add support for dropping multiple objects at once fro |
| Previous Message | Dave Page | 2018-10-31 10:09:45 | pgAdmin 4 commit: Allow the selection order to be preserved in the Sele |