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

From Dave Page
Subject pgAdmin 4 commit: Fixed 'Increment value cannot be empty' error for exi
Date
Msg-id E1hqZy1-0005aF-LG@gothos.postgresql.org
Whole thread Raw
List pgadmin-hackers
Fixed 'Increment value cannot be empty' error for existing tables. Fixes #4160

Branch
------
electron2

Details
-------
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=c52de1b3106adb599e3e252f322a2ea5ec05d19c
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: Akshay Joshi
Date:
Subject: pgAdmin 4 commit: Fix syntax error in query tool feature test for Pytho
Next
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Stop using application/x-javascript as a mime type an