| From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
|---|---|
| To: | Ganesh Jaybhay <ganesh(dot)jaybhay(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin][RM5007] Index should be visible using unique constraints |
| Date: | 2020-04-14 08:39:42 |
| Message-ID: | CANxoLDfKF-SyugwPvoasSfypiaH6Mdfnqy49g64=tzPewFnyCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Thanks, patch applied.
On Mon, Apr 13, 2020 at 5:51 PM Ganesh Jaybhay <
ganesh(dot)jaybhay(at)enterprisedb(dot)com> wrote:
> Hi Hackers,
> Please find the attached patch with below fixes:
>
> - Index dropdown should have existing indexes while creating unique
> constraint
> - On selecting index from index dropdown, other fields( should be empty
> and disabled (Applicable for Primary and unique key constraint)
> - Added test cases
>
> Please review.
>
> Regards,
> Ganesh Jaybhay
>
--
*Thanks & Regards*
*Akshay Joshi*
*Sr. Software Architect*
*EnterpriseDB Software India Private Limited*
*Mobile: +91 976-788-8246*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akshay Joshi | 2020-04-14 08:39:54 | Re: [pgAdmin4][Patch] - RM 5383 - Error related to OID displayed if Click on properties of synonym and Click on refresh button |
| Previous Message | Akshay Joshi | 2020-04-14 08:38:52 | pgAdmin 4 commit: Ensure index dropdown should have existing indexes wh |