When iDempiere generates the SQL update to the database is generating unnecessary settings for null columns.
For example, if you go to Tab Editor and change the order of a field, the SQL generated looks like this:
UPDATE AD_Field SET SeqNo=180, AD_Reference_Value_ID=NULL, AD_Val_Rule_ID=NULL, IsToolbarButton=NULL,Updated=TO_TIMESTAMP('2022-09-22 19:24:08','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Field_ID=5164
even when the columns AD_Reference_Value_ID, AD_Val_Rule_ID and IsToolbarButton are already null in the database.
AD_Reference_Value_ID
AD_Val_Rule_ID
IsToolbarButton
The command to generate must be simply:
UPDATE AD_Field SET SeqNo=180,Updated=TO_TIMESTAMP('2022-09-22 19:24:08','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Field_ID=5164
When iDempiere generates the SQL update to the database is generating unnecessary settings for null columns.
For example, if you go to Tab Editor and change the order of a field, the SQL generated looks like this:
UPDATE AD_Field SET SeqNo=180, AD_Reference_Value_ID=NULL, AD_Val_Rule_ID=NULL, IsToolbarButton=NULL,Updated=TO_TIMESTAMP('2022-09-22 19:24:08','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Field_ID=5164even when the columns
AD_Reference_Value_ID,AD_Val_Rule_IDandIsToolbarButtonare already null in the database.The command to generate must be simply:
UPDATE AD_Field SET SeqNo=180,Updated=TO_TIMESTAMP('2022-09-22 19:24:08','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Field_ID=5164