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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0009766
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] Z. Othersmajorhave not tried2009-07-03 15:382009-07-16 17:55
ReportershuehnerView Statuspublic 
Assigned Toshuehner 
PriorityimmediateResolutionno change requiredFixed in Version
StatusclosedFix in branchpiFixed 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

0009766: API change:api check: build 63 fails

DescriptionThe following API check build failed:

http://builds.openbravo.com/job/erp_devel_pi-module-integrity-test/63/console [^]

+++++++++++++++++++++++++++++++++++++++++++++++++++
  Errors in API model validation
+++++++++++++++++++++++++++++++++++++++++++++++++++
  Unique constraint added: table: C_EXTERNALPOS_CATEGORY - Unique constraint: C_EXTPOSCAT_PRODCATEGORY_UN
  Unique constraint added: table: C_EXTERNALPOS_CATEGORY - Unique constraint: C_EXTPOSCAT_PRODCATEGORY_UN
  Unique constraint added: table: C_EXTERNALPOS_PRODUCT - Unique constraint: C_EXTPOSPROD_PRODUCT_UN
  Unique constraint added: table: C_EXTERNALPOS_PRODUCT - Unique constraint: C_EXTPOSPROD_PRODUCT_UN
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0009808 closedalostale API model check: reports false positive when a column is added to an existing unique constraint. 

-  Notes
(0017894)
shuehner (administrator)
2009-07-03 15:42

This issue is a false positive of the model check.

The change did not introduce a new unique constraint.

Instead it added a new column to an existing unique constraint which makes the unique constraint less strict which is not a problem for existing users of the table.
(0017895)
shuehner (administrator)
2009-07-03 15:44

Estimate from @alostale is about 2-3h to change the model test to automatically ignore this special case of unique constraint changes.

Proposal:
1.) ignore manually and not document, as no api problem but a false positive in the test.
2.) possibly enhance the test?
(0017900)
pjuvara (reporter)
2009-07-03 19:13

Approved as false positive.

Please ignore this issue for now but also change the test.
(0018066)
shuehner (administrator)
2009-07-09 16:57

This was a false positive in the model check script. Issue 9808 fixed the check script so this issue here needs no change as the wrongly reported api violation is not reported anymore.

- Issue History
Date Modified Username Field Change
2009-07-03 15:38 shuehner New Issue
2009-07-03 15:38 shuehner Assigned To => rafaroda
2009-07-03 15:42 shuehner Note Added: 0017894
2009-07-03 15:44 shuehner Note Added: 0017895
2009-07-03 15:44 shuehner Assigned To rafaroda => pjuvara
2009-07-03 19:13 pjuvara Note Added: 0017900
2009-07-03 19:13 pjuvara Status new => scheduled
2009-07-03 19:13 pjuvara Assigned To pjuvara => shuehner
2009-07-03 19:13 pjuvara fix_in_branch => pi
2009-07-08 14:33 shuehner Relationship added related to 0009808
2009-07-09 16:57 shuehner Status scheduled => closed
2009-07-09 16:57 shuehner Note Added: 0018066
2009-07-09 16:57 shuehner Resolution open => no change required
2009-07-16 17:55 anonymous sf_bug_id 0 => 2822585


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker