Ensure that last row of table data should be visible and user will be able to add new row. Fixes #3866

This commit is contained in:
Aditya Toshniwal
2019-01-11 23:25:05 +05:30
committed by Akshay Joshi
parent 14f462e9dc
commit d4a2f1b8cd
3 changed files with 14 additions and 1 deletions

View File

@@ -2,7 +2,7 @@
Version 4.1
***********
Release date: 2019-02-07
Release date: 2019-01-15
This release contains a number of features and fixes reported since the release of pgAdmin4 4.0
@@ -19,4 +19,5 @@ Bug fixes
| `Bug #3836 <https://redmine.postgresql.org/issues/3836>`_ - Fix ordering of VACUUM options which changed in PG11.
| `Bug #3842 <https://redmine.postgresql.org/issues/3842>`_ - Don't show system catalogs in the schemas property list unless show system objects is enabled.
| `Bug #3861 <https://redmine.postgresql.org/issues/3861>`_ - Fix help for the backup/restore dialogues.
| `Bug #3866 <https://redmine.postgresql.org/issues/3866>`_ - Ensure that last row of table data should be visible and user will be able to add new row.
| `Bug #3877 <https://redmine.postgresql.org/issues/3877>`_ - Make the browser more robust in the face of multibyte characters in SQL_ASCII databases.