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

View Revisions: Issue #36984 All Revisions ] Back to Issue ]
Summary 0036984: Upgrading from 2.50 to pi some unique constraints are violated
Revision 2017-10-02 14:11 by inigosanchez
Description When upgrading from 2.50 to pi, some unique constraints are violating in the new database. See the log of the job[1] that raises the reported problem.

This occurs because an old window (2.5 window: Cost Center) has changes in its ID and a unique constraint depends on this change (unique constraint of ad_window: client_id, name, module_id). When alter the data in update.database task having this scenario, the order the data are loaded into the database are:
- insert: Cost Center - 79FC23AB84F04384B4B7CCCADCDD2942 -> ERROR BECAUSE (client, name, module) is in the database from 2.5
- update: Cost Center - 800030 to Manufacturing Cost Center - 800030 -> Is not executed for the error on insert

Before the changeset that introduces the regression, all the data changes were handled individually and under some lucky circumstances, all the data was updated properly.



[1].- https://ci.openbravo.com/job/up-2.50topi-pgsql/206/consoleText [^]
Revision 2017-10-02 13:52 by inigosanchez
Description When upgrading from 2.50 to pi, some unique constraints are violating in the new database. In the log of the job [1] that fails



[1].- https://ci.openbravo.com/job/up-2.50topi-pgsql/206/consoleText [^]


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker