Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0032921Openbravo ERPY. DBSourceManagerpublic2016-05-10 23:152017-09-25 10:30
Osmany 
inigosanchez 
normalminoralways
closedfixed 
5
 
3.0PR17Q4 
alostale
Core
No
0032921: Constraint and trigger remain after being eliminated in a template
Constraint and trigger remain after being eliminated in a template.

For example the following changes (Remove a trigger and a check constraint) are not applied using the build task install.source. However the build task update.database does apply properly the template changes:

+ <removeTriggerChange triggerName="A_AMORTIZATION_TRG"/>
+ <removeCheckChange tableName="A_AMORTIZATION" checkName="A_AMORTIZATION_ISACTIVE_CHECK">
+ <check name="A_AMORTIZATION_ISACTIVE_CHECK"><![CDATA[ISACTIVE IN ('Y', 'N')]]></check>
+ </removeCheckChange>
1. Login in the ERP as "System Administrator - System"
2. Go to [Module] window and set org.openbravo.v3 template in development. Logout.
3. Delete a constraint and trigger from the db.
4. Execute an export.database task.
5. Execute an export.config.script.
- VERIFY in the configScript file the elimination of constraint and trigger.
6. Execute an install.source task.
- ERROR: Does not remove the constraint and trigger in the database.
SER-QA
related to defect 0036137 closed inigosanchez [SER-QA 2918] Config script removeCheckChange are not applied on install.source 
Issue History
2016-05-10 23:15OsmanyNew Issue
2016-05-10 23:15OsmanyAssigned To => platform
2016-05-10 23:15OsmanyModules => Core
2016-05-10 23:15OsmanyTriggers an Emergency Pack => No
2016-05-12 12:08adrianromeroResolution time => 1463608800
2016-05-12 12:08adrianromeroTag Attached: SER-QA
2016-05-18 13:42alostaleNote Added: 0086549
2016-05-18 13:42alostaleAssigned Toplatform => adrianromero
2016-05-18 13:42alostaleStatusnew => feedback
2016-05-18 16:29OsmanyNote Added: 0086552
2016-05-18 16:40adrianromeroPriorityhigh => normal
2016-05-18 16:40adrianromeroSeveritymajor => minor
2016-05-18 16:40adrianromeroStatusfeedback => new
2016-05-18 16:40adrianromeroSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=12149#r12149
2016-05-18 16:40adrianromeroAssigned Toadrianromero => alostale
2016-05-18 16:41adrianromeroSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=12150#r12150
2016-05-18 17:45alostaleAssigned Toalostale => platform
2016-05-18 17:45alostaleStatusnew => acknowledged
2016-05-23 08:35alostaleResolution time1463608800 =>
2017-07-26 11:24alostaleRelationship addedrelated to 0036137
2017-09-25 10:13inigosanchezStatusacknowledged => scheduled
2017-09-25 10:13inigosanchezAssigned Toplatform => inigosanchez
2017-09-25 10:25inigosanchezDescription Updatedbug_revision_view_page.php?rev_id=15977#r15977
2017-09-25 10:25inigosanchezSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=15978#r15978
2017-09-25 10:26inigosanchezDescription Updatedbug_revision_view_page.php?rev_id=15979#r15979
2017-09-25 10:30inigosanchezReview Assigned To => alostale
2017-09-25 10:30inigosanchezNote Added: 0099514
2017-09-25 10:30inigosanchezStatusscheduled => closed
2017-09-25 10:30inigosanchezResolutionopen => fixed
2017-09-25 10:30inigosanchezFixed in Version => 3.0PR17Q4

Notes
(0086549)
alostale   
2016-05-18 13:42   
feedback request:

1. Be more specific in the reporting: what constraint do you remove, does it also apply to update.database...
2. Review severity
(0086552)
Osmany   
2016-05-18 16:29   
You can test with any constraint and trigger. When applies update.database working fine. The problem is with install.source task.
(0099514)
inigosanchez   
2017-09-25 10:30   
Since the 0036137 was fixed, this issue is not reproduced anymore. Verified reported flow: now the constraint and the trigger are not remained in the db and the are removed properly.