Contents
- Getting Started
- External database for pgAdmin user settings
- Connecting To A Server
- Managing Cluster Objects
- Managing Database Objects
- Creating or Modifying a Table
- Management Basics
- Backup and Restore
- Developer Tools
- Processes
- pgAgent
- pgAdmin Project Contributions
- Release Notes
- Version 7.8
- Version 7.7
- Version 7.6
- Version 7.5
- Version 7.4
- Version 7.3
- Version 7.2
- Version 7.1
- Version 7.0
- Version 6.21
- Version 6.20
- Version 6.19
- Version 6.18
- Version 6.17
- Version 6.16
- Version 6.15
- Version 6.14
- Version 6.13
- Version 6.12
- Version 6.11
- Version 6.10
- Version 6.9
- Version 6.8
- Version 6.7
- Version 6.6
- Version 6.5
- Version 6.4
- Version 6.3
- Version 6.2
- Version 6.1
- Version 6.0
- Version 5.7
- Version 5.6
- Version 5.5
- Version 5.4
- Version 5.3
- Version 5.2
- Version 5.1
- Version 5.0
- Version 4.30
- Version 4.29
- Version 4.28
- Version 4.27
- Version 4.26
- Version 4.25
- Version 4.24
- Version 4.23
- Version 4.22
- Version 4.21
- Version 4.20
- Version 4.19
- Version 4.18
- Version 4.17
- Version 4.16
- Version 4.15
- Version 4.14
- Version 4.13
- Version 4.12
- Version 4.11
- Version 4.10
- Version 4.9
- Version 4.8
- Version 4.7
- Version 4.6
- Version 4.5
- Version 4.4
- Version 4.3
- Version 4.2
- Version 4.1
- Version 4.0
- Version 3.6
- Version 3.5
- Version 3.4
- Version 3.3
- Version 3.2
- Version 3.1
- Version 3.0
- Version 2.1
- Version 2.0
- Version 1.6
- Version 1.5
- Version 1.4
- Version 1.3
- Version 1.2
- Version 1.1
- Version 1.0
- Licence
Version 4.6¶
Release date: 2019-05-02
This release contains a number of new features and fixes reported since the release of pgAdmin4 4.5
Features¶
Issue #4165 - Depend on psycopg2-binary in the Python wheel, rather than psycopg2.
Bug fixes¶
Issue #2392 - Ensure that on clicking Delete button should not delete rows immediately from the database server, it should be deleted when Save button will be clicked.
Issue #3327 - Ensure that newly added row in backgrid should be visible.
Issue #3582 - Ensure that JSON strings as comments should be added properly for all the objects.
Issue #3605 - Fix an issue where Deleting N number of rows makes first N number of rows disable.
Issue #3938 - Added support for Default Partition.
Issue #4087 - Fix an issue where ‘GRANT UPDATE’ sql should be displayed for default sequence privileges.
Issue #4101 - Ensure that confirmation dialog should be popped up before reload of query tool or debugger if it is opened in a new browser tab.
Issue #4104 - Ensure that record should be add/edited for root partition table with primary keys.
Issue #4121 - Fixed alignment issue of columns in definition section of Index node.
Issue #4134 - Fixed ‘Location cannot be empty’ error when open Tablespace properties.
Issue #4138 - Fix an issue where the dropdown becomes misaligned/displaced.
Issue #4154 - Ensure the treeview shows all sequences except those used to implement IDENTITY columns (which can be edited as part of the column). Show all if Show System Objects is enabled.
Issue #4160 - Fixed ‘Increment value cannot be empty’ error for existing tables.
Issue #4161 - Ensure that parameters of procedures for EPAS server 10 and below should be set/reset properly.
Issue #4163 - Prevent duplicate columns being included in reverse engineered SQL for tables.
Issue #4182 - Ensure sanity of the permissions on the storage and session directories and the config database.