pgAdmin 4 commit: Fixed 'Increment value cannot be empty' error for exi

From: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
To: pgadmin-hackers(at)lists(dot)postgresql(dot)org
Subject: pgAdmin 4 commit: Fixed 'Increment value cannot be empty' error for exi
Date: 2019-04-22 06:35:01
Message-ID: E1hISXd-0001N5-1E@gothos.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Fixed 'Increment value cannot be empty' error for existing tables. Fixes #4160

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=5452bff49e1b35705274711e603d5cb01be62a6a
Author: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>

Modified Files
--------------
docs/en_US/release_notes_4_6.rst | 1 +
.../databases/schemas/tables/columns/static/js/column.js | 12 +++++++++++-
2 files changed, 12 insertions(+), 1 deletion(-)

Browse pgadmin-hackers by date

  From Date Subject
Next Message Akshay Joshi 2019-04-22 06:35:31 Re: [pgAdmin4][Patch] - RM 4160 - (Re-)Edit column properties blocked to "Increment value cannot be empty" error.
Previous Message Khushboo Vashi 2019-04-22 06:18:13 [pgAdmin4][Patch] - RM 4087 - Default sequence privileges does not show update grant