pgAdmin 4 commit: Fixed 'Increment value cannot be empty' error for exi - Mailing list pgadmin-hackers

From Akshay Joshi
Subject pgAdmin 4 commit: Fixed 'Increment value cannot be empty' error for exi
Date
Msg-id E1hISXd-0001N5-1E@gothos.postgresql.org
Whole thread Raw
List 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.vashi@enterprisedb.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(-)


pgadmin-hackers by date:

Previous
From: Khushboo Vashi
Date:
Subject: [pgAdmin4][Patch] - RM 4087 - Default sequence privileges does notshow update grant
Next
From: Akshay Joshi
Date:
Subject: Re: [pgAdmin4][Patch] - RM 4160 - (Re-)Edit column properties blockedto "Increment value cannot be empty" error.