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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0012577
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] Y. DBSourceManagermajorhave not tried2010-03-05 15:122018-04-08 17:01
ReportershuehnerView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0012577: 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 [^]
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 00279183.0PR15Q1 closedAugustoMauch After PR14Q2.X and new tree infrastructure, window User Defined Accounting Report Setup window has lost the tree view 

-  Notes
(0044703)
marvintm (developer)
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 (developer)
2012-09-24 23:36

Effort: 10
Impact: low
Plan: mid

- Issue History
Date Modified Username Field Change
2010-03-05 15:12 shuehner New Issue
2010-03-05 15:12 shuehner Assigned To => marvintm
2010-03-05 15:15 shuehner Summary dbsourcemanager 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:58 alostale Status new => scheduled
2010-03-08 15:58 alostale fix_in_branch => pi
2012-01-30 15:24 marvintm Note Added: 0044703
2012-01-30 15:24 marvintm Type defect => design defect
2012-01-30 15:24 marvintm fix_in_branch pi =>
2012-09-24 23:36 AugustoMauch Note Added: 0052501
2012-09-24 23:36 AugustoMauch Priority urgent => normal
2014-10-21 12:32 AugustoMauch Relationship added related to 0027918
2018-04-08 17:01 shuehner Assigned To marvintm => platform


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker