Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #34102 Back to Issue ]
Summary 0034102: Update.database and Install.Source tasks should use the same flow to create the database and the db model
Revision 2017-06-08 20:48 by inigosanchez
Description Update.database and Install.Source tasks should use the same flow to create the database and the db model. Currently there is duplicated code that is handling those tasks separately. This causes that the behavior is different when applying some model changes.

For example, currently DB Source Manager supports the exportation of the following changes into a Configuration Script[1]:

- Remove Trigger
- Column Required
- Column Size
- Column Data

But on install.source task it is only possible to apply these changes: Column Size, Column Data and Remove Check. See[2].

The Remove Check change is supported on install.source since the resolution of issue 0036137, but still it is being handled in a different flow from the update.database task.

[1] http://wiki.openbravo.com/wiki/ERP_2.50:Developers_Guide/How_To_Create_a_Configuration_Script [^]

[2] https://code.openbravo.com/erp/devel/dbsm-main/file/482384f24ab9/src/org/apache/ddlutils/platform/SqlBuilder.java#l4504 [^]
Revision 2017-06-08 13:19 by caristu
Description Update.database and Install.Source tasks should use the same flow to create the database and the db model. Currently there is duplicated code that is handling those tasks separately. This causes that the behavior is different when applying some model changes.

For example, currently DB Source Manager supports the exportation of the following changes into a Configuration Script[1]:

- Remove Trigger
- Remove Check
- Column Required
- Column Size
- Column Data

But on install.source task it is only possible to apply these changes: Column Size, Column Data and Remove Check. See[2].

The Remove Check change is supported on install.source since the resolution of issue 0036137, but still it is being handled in a different flow from the update.database task.

[1] http://wiki.openbravo.com/wiki/ERP_2.50:Developers_Guide/How_To_Create_a_Configuration_Script [^]

[2] https://code.openbravo.com/erp/devel/dbsm-main/file/482384f24ab9/src/org/apache/ddlutils/platform/SqlBuilder.java#l4504 [^]
Revision 2017-06-06 17:43 by caristu
Description Currently DB Source Manager supports the exportation of the following changes into a Configuration Script[1]:

- Remove Trigger
- Remove Check
- Column Required
- Column Size
- Column Data

But on install.source task it is only possible to apply the last two types of changes. See[2].


[1] http://wiki.openbravo.com/wiki/ERP_2.50:Developers_Guide/How_To_Create_a_Configuration_Script [^]

[2] https://code.openbravo.com/erp/devel/dbsm-main/file/482384f24ab9/src/org/apache/ddlutils/platform/SqlBuilder.java#l4504 [^]
Revision 2016-09-27 16:49 by caristu
Steps To Reproduce 1) Create a new Template and place the attached configuration script into the src-db/database folder. Notice that the config script is intended to turn into false the required property of the C_CURRENCY_ID column in the A_AMORTIZATION_TABLE
2) Run install.source. Notice that the C_CURRENCY_ID is still mandatory --> check the database: the change has NOT been applied
3) Run ant update.database. Notice that the C_CURRENCY_ID is not mandatory --> check the database: the change has been applied
Revision 2016-09-27 16:49 by caristu
Steps To Reproduce 1) Create a new Template and place the attached configuration script into the src-db/database folder. Notice that the config script is intended to turn into false the required property of the C_CURRENCY_ID column in the A_AMORTIZATION_TABLE
2) Run install.source. Notice that the C_CURRENCY_ID is still mandatory --> the change has NOT been applied
3) Run ant update.database. Notice that the C_CURRENCY_ID is not mandatory --> the change has been applied
Revision 2016-09-27 16:47 by caristu
Steps To Reproduce 1) Create a new Template and place the attached configuration script into the src-db/database folder. Notice that the config script is intended to turn into false the required property of the C_CURRENCY_ID column in the A_AMORTIZATION_TABLE

2) Run install.source. Notice that the C_CURRENCY_ID is still mandatory --> the change has NOT been applied
3) Run ant update.database. Notice that the C_CURRENCY_ID is not mandatory --> the change has been applied


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker