Project:
| View Revisions: Issue #25744 | [ Back to Issue ] | ||
| Summary | 0025744: Problems during the rebuild | ||
| Revision | 2014-02-17 10:04 by jecharri | ||
| Steps To Reproduce | -create 2 tables --> "sn_table_inv" and "sl_table_inv" -two tables should have a foreign key to same table. For example "c_bpartner" table Execute "ant smartbuild -Dlocal=no" command and you will get similar error to: [java] 0 [main] INFO org.openbravo.base.model.ModelProvider - Building runtime model [java] 12158 [main] ERROR org.openbravo.base.model.NamingUtil - ERROR: Property name computation fails for property BusinessPartner.null using new name tableInvCustomerList there is more then one property with the same name, being robust and renaming property automatically. If this error appears during update.database then this is possibly solved automatically. Otherwise this should be repaired manually by changing the AD_Column.name of the column C_BPartner.null Above error will create a BusinessPartner entity with 2 similar properties: -PROPERTY_TABLEINVCUSTOMERLIST -PROPERTY_TABLEINVCUSTOMERLIST185 Due to that, the developer could have problems if he or she was using method getTableInvCustomerList. |
||
| Revision | 2014-02-17 10:04 by jecharri | ||
| Description | Problems during the rebuild. The problems happens when you have 2 tables with same name but different databse prefix doing reference to same table |
||
| Revision | 2014-02-17 10:04 by jecharri | ||
| Steps To Reproduce | -create 2 tables --> "sn_table_inv" and "sl_table_inv" -two tables should have a foreign key to same table. For example "c_bpartner" table Execute "ant smartbuild -Dlocal=no" command and you will get similar error to: [java] 0 [main] INFO org.openbravo.base.model.ModelProvider - Building runtime model [java] 12158 [main] ERROR org.openbravo.base.model.NamingUtil - ERROR: Property name computation fails for property BusinessPartner.null using new name tableInvCustomerList there is more then one property with the same name, being robust and renaming property automatically. If this error appears during update.database then this is possibly solved automatically. Otherwise this should be repaired manually by changing the AD_Column.name of the column C_BPartner.null |
||
| Revision | 2014-02-17 10:04 by AugustoMauch | ||
| Description | Problems during the rebuild. The problems happens when you have 2 tables with same name but different database prefix being referenced from the same table |
||
| Revision | 2014-02-17 10:02 by AugustoMauch | ||
| Description | Problems during the rebuild. The problems happens when you have 2 tables with same name but different databse prefix doing reference to same table |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |