Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] Z. Othersmajorhave not tried2012-11-19 09:572013-01-18 09:34
ReporterioritzCiaView Statuspublic 
Assigned ToioritzCia 
PriorityimmediateResolutionfixedFixed in Version
StatusclosedFix in branchpiFixed in SCM revision751258826d60
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_22
OS VersionUbuntu 10.04Database version8.4Ant version1.7.1
Product VersionSCM revision 
Review Assigned To
Web browserGoogle Chrome
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0022339: Fix to issue 21886 causes an api change.

DescriptionDue to this issue: [^]

I have to make an api-change. This is the change: [^]

Due to this issue [^] api change does not detect the change, so I cannot paste the failure.

- The change is the following:
M_PRODUCT_PO.VENDORPRODUCTNO column goes from not nullable to nullable.

- The change is required due to the following reason:
This column is in a unique constraint that needs to be removed due to 21886 issue. The unique constraint is that each product needs to have one unique vendorproductno for each business partner and this is not right, because two partners may have the same vendortproductno for the same product.

- The risk is low:
Someone may have made a development assuming this field would never be null. If that development did not have the null check and now that column is allowed to be null, it would cause an exception. Anyway these should not be very likely.
Steps To ReproduceNone.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
depends on defect 00218863.0MP18 closedjecharri Restrictions in M_PRODUCT_PO can not be enforced 

-  Notes
iciordia (manager)
2012-11-19 11:31


ioritzCia (developer)
2012-11-19 13:36

No change fixes this API-Change. As said in the description, due to issue 21176 this will not fail in the tests. The SCM revision was set to the original issue's fix as the field is mandatory.

- Issue History
Date Modified Username Field Change
2012-11-19 09:57 ioritzCia New Issue
2012-11-19 09:57 ioritzCia Assigned To => dmiguelez
2012-11-19 09:57 ioritzCia Web browser => Google Chrome
2012-11-19 09:57 ioritzCia Modules => Core
2012-11-19 09:57 ioritzCia Web browser Google Chrome => Google Chrome
2012-11-19 09:57 ioritzCia Assigned To dmiguelez => iciordia
2012-11-19 09:57 ioritzCia Status new => feedback
2012-11-19 11:32 iciordia Note Added: 0054302
2012-11-19 11:32 iciordia Assigned To iciordia => ioritzCia
2012-11-19 11:32 iciordia Status feedback => scheduled
2012-11-19 11:32 iciordia fix_in_branch => pi
2012-11-19 13:23 ioritzCia Relationship added depends on 0021886
2012-11-19 13:36 ioritzCia Note Added: 0054313
2012-11-19 13:36 ioritzCia Status scheduled => resolved
2012-11-19 13:36 ioritzCia Fixed in SCM revision => 751258826d60
2012-11-19 13:36 ioritzCia Resolution open => fixed
2013-01-18 09:34 ioritzCia Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker