Project:
| View Revisions: Issue #32921 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0032921: Constraint and trigger remain after being eliminated in a template | ||
| Revision | 2017-09-25 10:26 by inigosanchez | ||
| Description | 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> |
||
| Revision | 2017-09-25 10:25 by inigosanchez | ||
| Description | 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> |
||
| Revision | 2017-09-25 10:13 by inigosanchez | ||
| Description | Constraint and trigger remain after being eliminated in a template | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |