Re: [pgAdmin4][Patch] - RM 4160 - (Re-)Edit column properties blocked to "Increment value cannot be empty" error.

From: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
To: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [pgAdmin4][Patch] - RM 4160 - (Re-)Edit column properties blocked to "Increment value cannot be empty" error.
Date: 2019-04-22 06:35:31
Message-ID: CANxoLDeq3syLhZjLzKu+udNCW6rGHosqC0D1qfo28D-jRH9o=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Thanks patch applied.

On Fri, Apr 19, 2019 at 11:10 AM Khushboo Vashi <
khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:

> Hi,
>
> Please find the attached patch to fix the RM #4160 - (Re-)Edit column
> properties blocked to "Increment value cannot be empty" error.
>
> Thanks,
> Khushboo
>
>

--
*Thanks & Regards*
*Akshay Joshi*

*Sr. Software Architect*
*EnterpriseDB Software India Private Limited*
*Mobile: +91 976-788-8246*

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Akshay Joshi 2019-04-22 06:54:58 pgAdmin 4 commit: Fix an issue where 'GRANT UPDATE' sql should be displ
Previous Message Akshay Joshi 2019-04-22 06:35:01 pgAdmin 4 commit: Fixed 'Increment value cannot be empty' error for exi