Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009766Openbravo ERPZ. Otherspublic2009-07-03 15:382009-07-16 17:55
Reportershuehner 
Assigned Toshuehner 
PriorityimmediateSeveritymajorReproducibilityhave not tried
StatusclosedResolutionno change required 
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
Summary0009766: 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
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0009808 closed alostale API model check: reports false positive when a column is added to an existing unique constraint. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-07-03 15:38shuehnerNew Issue
2009-07-03 15:38shuehnerAssigned To => rafaroda
2009-07-03 15:42shuehnerNote Added: 0017894
2009-07-03 15:44shuehnerNote Added: 0017895
2009-07-03 15:44shuehnerAssigned Torafaroda => pjuvara
2009-07-03 19:13pjuvaraNote Added: 0017900
2009-07-03 19:13pjuvaraStatusnew => scheduled
2009-07-03 19:13pjuvaraAssigned Topjuvara => shuehner
2009-07-03 19:13pjuvarafix_in_branch => pi
2009-07-08 14:33shuehnerRelationship addedrelated to 0009808
2009-07-09 16:57shuehnerStatusscheduled => closed
2009-07-09 16:57shuehnerNote Added: 0018066
2009-07-09 16:57shuehnerResolutionopen => no change required
2009-07-16 17:55anonymoussf_bug_id0 => 2822585

Notes
(0017894)
shuehner   
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   
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   
2009-07-03 19:13   
Approved as false positive.

Please ignore this issue for now but also change the test.
(0018066)
shuehner   
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.