Project:
| View Revisions: Issue #18793 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0018793: try-2.50-api has failed because one column has been change | ||
| Revision | 2011-10-18 09:07 by jecharri | ||
| Description | Due to this issue, - https://issues.openbravo.com/view.php?id=18413 [^] I have to make an api change. This is the change: - https://code.openbravo.com/erp/stable/2.50/rev/2252a735b722 [^] I have pushed the change to r2.50 and this is the failure: - http://builds.openbravo.com/view/r2.50/job/2.50-api/262/console [^] -The change is the following: The column "SOCIAL_NAME" from AD_ORG table has been change from VARCHAR to NVARCHAR.So, now it is posible to put the same quantity of characters in Postgre and Oracle - The risk of this api change is very low or cero because of the following reason: For the moment this column only has bee published in MP4 and any module or core funcionalities use it. So this column has never been used for the moment |
||
| Revision | 2011-10-18 09:04 by jecharri | ||
| Description | Due to this issue, - https://issues.openbravo.com/view.php?id=18413 [^] I have to make an api change. This is the change: - https://code.openbravo.com/erp/stable/2.50/rev/2252a735b722 [^] I have pushed the change to r2.50 and this is the failure: - http://builds.openbravo.com/view/r2.50/job/2.50-api/262/console [^] -The change is the following: The column "SOCIAL_NAME" from AD_ORG table has been change from VARCHAR to NVARCHAR.So, now it is posible to put the same quantity of characters in Postgre and Oracle - The risk of this api change is very low or cero because of the following reason: I have only give the posiblity to have the same quantity of characters in Oracle or Postgre to social name column. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |