Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0027195 | Openbravo ERP | Z. Others | public | 2014-07-25 11:50 | 2014-07-28 13:26 |
Reporter | AtulOpenbravo | ||||
Assigned To | shuehner | ||||
Priority | normal | Severity | trivial | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | No | ||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0027195: Change api-check tool to remove ignoring 'add one column to existing unique constraint' | ||||
Description | 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. | ||||
Steps To Reproduce | - | ||||
Proposed Solution | Change ValidateAPIModel file to remove the special case so far permitting this change mentioned above. | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2014-07-25 11:50 | AtulOpenbravo | New Issue | |||
2014-07-25 11:50 | AtulOpenbravo | Assigned To | => shuehner | ||
2014-07-25 11:50 | AtulOpenbravo | OBNetwork customer | => No | ||
2014-07-25 11:50 | AtulOpenbravo | Modules | => Core | ||
2014-07-25 11:50 | AtulOpenbravo | Triggers an Emergency Pack | => No | ||
2014-07-28 13:26 | shuehner | Category | 01. General setup => Z. Others | ||
2014-07-28 13:26 | shuehner | Summary | API 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:26 | shuehner | Description Updated | bug_revision_view_page.php?rev_id=6197#r6197 | ||
2014-07-28 13:26 | shuehner | Proposed Solution updated |
There are no notes attached to this issue. |