Project:
| View Revisions: Issue #27195 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0027195: Change api-check tool to remove ignoring 'add one column to existing unique constraint' | ||
| Revision | 2014-07-28 13:26 by shuehner | ||
| 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. |
||
| Revision | 2014-07-25 11:50 by shuehner | ||
| Description | Ability to define business partner with same search key in different organization of the same client. Added one more key AD_Org_ID in the existing unique constraint along with AD_Client_ID and Value. | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |