Fixed object delete issue from the properties tab for the collection nodes. Fixes #6858

This commit is contained in:
Rahul Shirsat 2021-10-19 17:21:46 +05:30 committed by Akshay Joshi
parent a2f5e6ad8f
commit 27b6e07e21
4 changed files with 4 additions and 1 deletions

View File

@ -30,6 +30,7 @@ Bug fixes
| `Issue #6797 <https://redmine.postgresql.org/issues/6797>`_ - Remove an extra blank line at the start of the SQL for function, procedure, and trigger function. | `Issue #6797 <https://redmine.postgresql.org/issues/6797>`_ - Remove an extra blank line at the start of the SQL for function, procedure, and trigger function.
| `Issue #6802 <https://redmine.postgresql.org/issues/6802>`_ - Fixed the issue of editing triggers for advanced servers. | `Issue #6802 <https://redmine.postgresql.org/issues/6802>`_ - Fixed the issue of editing triggers for advanced servers.
| `Issue #6828 <https://redmine.postgresql.org/issues/6828>`_ - Fixed an issue where the tree is not scrolling to the object selected from the search result. | `Issue #6828 <https://redmine.postgresql.org/issues/6828>`_ - Fixed an issue where the tree is not scrolling to the object selected from the search result.
| `Issue #6858 <https://redmine.postgresql.org/issues/6858>`_ - Fixed object delete issue from the properties tab for the collection nodes.
| `Issue #6876 <https://redmine.postgresql.org/issues/6876>`_ - Ensure that the Dashboard should get updated after connecting to the server. | `Issue #6876 <https://redmine.postgresql.org/issues/6876>`_ - Ensure that the Dashboard should get updated after connecting to the server.
| `Issue #6881 <https://redmine.postgresql.org/issues/6881>`_ - Fixed an issue where the browser tree doesn't show all contents on changing resolution. | `Issue #6881 <https://redmine.postgresql.org/issues/6881>`_ - Fixed an issue where the browser tree doesn't show all contents on changing resolution.
| `Issue #6882 <https://redmine.postgresql.org/issues/6882>`_ - Ensure that columns should be displayed in the order of creation instead of alphabetical order in the browser tree. | `Issue #6882 <https://redmine.postgresql.org/issues/6882>`_ - Ensure that columns should be displayed in the order of creation instead of alphabetical order in the browser tree.

View File

@ -44,6 +44,7 @@ define('pgadmin.node.constraints', [
pgBrowser.add_menus([]); pgBrowser.add_menus([]);
}, },
model: pgAdmin.Browser.Node.Model.extend({ model: pgAdmin.Browser.Node.Model.extend({
idAttribute: 'oid',
defaults: { defaults: {
name: undefined, name: undefined,
oid: undefined, oid: undefined,

View File

@ -319,6 +319,7 @@ function(
return getNodePartitionTableSchema(treeNodeInfo, itemNodeData, pgBrowser); return getNodePartitionTableSchema(treeNodeInfo, itemNodeData, pgBrowser);
}, },
model: pgBrowser.Node.Model.extend({ model: pgBrowser.Node.Model.extend({
idAttribute: 'oid',
defaults: { defaults: {
name: undefined, name: undefined,
oid: undefined, oid: undefined,

View File

@ -79,9 +79,9 @@ define('pgadmin.node.type', [
yet migrated to new react schema. Once the properties for collection yet migrated to new react schema. Once the properties for collection
is removed, remove this model */ is removed, remove this model */
model: pgBrowser.Node.Model.extend({ model: pgBrowser.Node.Model.extend({
idAttribute: 'oid',
defaults: { defaults: {
name: undefined, name: undefined,
oid: undefined,
is_sys_type: false, is_sys_type: false,
typtype: undefined, typtype: undefined,
}, },