Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012577Openbravo ERPY. DBSourceManagerpublic2010-03-05 15:122022-02-01 08:08
Reportershuehner 
Assigned ToTriage Platform Base 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusscheduledResolutionopen 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0012577: dbsourcemanager cannot to an ad_column.name update of two columns with intermediate conflicting values like A->B,B->C
DescriptionWhen the following situation is in the DB (unique constraint on ad_column.name)

first row with ad_column.name = A
second row with ad_column.name = B

then in on update.database both columns as renamed at once so

first A->B
then B->C

and second row has a higher uuid then the first row

then the update will fails as both renamings are applied individually and after the first there will be two rows with value B. which contradicts the unique constraint
Steps To Reproducesee this inc-build failing:
http://builds.openbravo.com/job/erp_devel_pi-inc-pgsql/1675/console [^]

after this commit:

https://code.openbravo.com/erp/devel/pi/rev/45b8e0cdb556 [^]
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00279183.0PR15Q1 closed AugustoMauch After PR14Q2.X and new tree infrastructure, window User Defined Accounting Report Setup window has lost the tree view 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-03-05 15:12shuehnerNew Issue
2010-03-05 15:12shuehnerAssigned To => marvintm
2010-03-05 15:15shuehnerSummarydbsourcemanager cannot to an ad_column.name update ot two columns with intermediate conflicts, A->B,B->C => dbsourcemanager cannot to an ad_column.name update of two columns with intermediate conflicting values like A->B,B->C
2010-03-08 15:58alostaleStatusnew => scheduled
2010-03-08 15:58alostalefix_in_branch => pi
2012-01-30 15:24marvintmNote Added: 0044703
2012-01-30 15:24marvintmTypedefect => design defect
2012-01-30 15:24marvintmfix_in_branchpi =>
2012-09-24 23:36AugustoMauchNote Added: 0052501
2012-09-24 23:36AugustoMauchPriorityurgent => normal
2014-10-21 12:32AugustoMauchRelationship addedrelated to 0027918
2018-04-08 17:01shuehnerAssigned Tomarvintm => platform
2022-02-01 08:08alostaleAssigned Toplatform => Triage Platform Base

Notes
(0044703)
marvintm   
2012-01-30 15:24   
This problem is real. However, it would require a significant change either in the way constraints are handled in dbsourcemanager (with a big performance penalty), or in the way data changes are executed, for it to be fixed, with a relevant risk of producing regressions.

Therefore, it is being changed to a design defect.
(0052501)
AugustoMauch   
2012-09-24 23:36   
Effort: 10
Impact: low
Plan: mid