Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0044896Openbravo ERPY. DBSourceManagerpublic2020-08-26 11:432024-11-06 11:06
caristu 
Triage Platform Base 
highminorN/A
newopen 
5
 
 
Core
No
0044896: Add check for dangerous operations in update.database task
It would be nice to ha

The taks will be executed in two steps

1. prepare everything without applying the database changes
2. check for dangerous operations like table recreation, table re-write due to not null new column, etc.
3a. do not proceed with the update as dangerous operations are detected. In this situation update would be only run if acknowledged but it might allow to do manual actions if feasible.
3b. proceed with the update as no dangerous operations are detected.
N/A
No tags attached.
related to defect 0044892 closed alostale On install.source config scripts are applied in two steps 
related to defect 0044612 closed Triage Platform Base ORA fails applying changes to columns used in functional indexes 
Issue History
2020-08-26 11:43caristuNew Issue
2020-08-26 11:43caristuAssigned To => platform
2020-08-26 11:43caristuModules => Core
2020-08-26 11:43caristuTriggers an Emergency Pack => No
2020-08-26 11:43caristuIssue generated from0044892
2020-08-26 11:43caristuRelationship addedrelated to 0044892
2020-08-26 11:43caristuRelationship addedrelated to 0044612
2022-02-01 08:07alostaleAssigned Toplatform => Triage Platform Base
2024-11-06 11:06shuehnerNote Added: 0171506

Notes
(0171506)
shuehner   
2024-11-06 11:06   
Note that 2nd part of item 2.) of the description is no longer an issue since PostgreSQL >=11
Since 11 adding table with a not null constraint does no longer trigger a table rewrite (on postgres side)