Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0027195Openbravo ERPZ. Otherspublic2014-07-25 11:502014-07-28 13:26
AtulOpenbravo 
shuehner 
normaltrivialhave not tried
newopen 
5
 
 
No
Core
No
0027195: Change api-check tool to remove ignoring 'add one column to existing unique constraint'
Currently when changing an existing unique constraint to be less strict api-check tools does not flag this as an api-change, as no existing data can exist failing the check.

However code which did rely on the stricter definition of the data can/will fail now as it may see more then one row now for its filter.

Example:
Table: c_bpartner
Old constraint: ad_client_id, value

New constraint: ad_client_id, ad_org_id, value

Here code relying on c_bpartner.value being unique within a single client will now fail after that change.

-
Change ValidateAPIModel file to remove the special case so far permitting this change mentioned above.
No tags attached.
Issue History
2014-07-25 11:50AtulOpenbravoNew Issue
2014-07-25 11:50AtulOpenbravoAssigned To => shuehner
2014-07-25 11:50AtulOpenbravoOBNetwork customer => No
2014-07-25 11:50AtulOpenbravoModules => Core
2014-07-25 11:50AtulOpenbravoTriggers an Emergency Pack => No
2014-07-28 13:26shuehnerCategory01. General setup => Z. Others
2014-07-28 13:26shuehnerSummaryAPI Change: Update unique constraint C_Bpartner_Value => Change api-check tool to remove ignoring 'add one column to existing unique constraint'
2014-07-28 13:26shuehnerDescription Updatedbug_revision_view_page.php?rev_id=6197#r6197
2014-07-28 13:26shuehnerProposed Solution updated

There are no notes attached to this issue.