Fixed an issue where the wrong SQL is generated when deleting and renaming table columns together. Fixes #6935

This commit is contained in:
Aditya Toshniwal 2021-10-19 17:13:12 +05:30 committed by Akshay Joshi
parent ea0d3eb812
commit a2f5e6ad8f
2 changed files with 2 additions and 1 deletions

View File

@ -43,3 +43,4 @@ Bug fixes
| `Issue #6928 <https://redmine.postgresql.org/issues/6928>`_ - Ensure that the master password should be prompt when MASTER_PASSWORD_REQUIRED is set to True and AUTHENTICATION_SOURCES is webserver.
| `Issue #6929 <https://redmine.postgresql.org/issues/6929>`_ - Ensure that only the table node should be allowed to drop on the ERD tool.
| `Issue #6930 <https://redmine.postgresql.org/issues/6930>`_ - Fixed an issue where the existing server group is disappeared on rename it.
| `Issue #6935 <https://redmine.postgresql.org/issues/6935>`_ - Fixed an issue where the wrong SQL is generated when deleting and renaming table columns together.

View File

@ -176,7 +176,7 @@ function getChangedData(topSchema, viewHelperProps, sessData, stringify=false, i
/* If the id attr value is present, then only changed keys can be passed.
Otherwise, passing all the keys is useful */
let idAttrValue = _.get(origVal, [field.id, rowIndx, field.schema.idAttribute]);
let idAttrValue = _.get(sessVal, [field.id, rowIndx, field.schema.idAttribute]);
if(_.isUndefined(idAttrValue)) {
change['changed'].push({
...changedRow,