Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0021591 | Openbravo ERP | A. Platform | public | 2012-09-10 17:07 | 2012-09-11 12:36 | |||||||
Reporter | marvintm | |||||||||||
Assigned To | marvintm | |||||||||||
Priority | urgent | Severity | major | Reproducibility | have not tried | |||||||
Status | closed | Resolution | duplicate | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | ||||||||||||
Target Version | 3.0MP16 | 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 | 0021591: AD_Module_Id column in AD_Ref_data_loaded should not have reference tabledir | |||||||||||
Description | Currently, the AD_Module_Id column in the AD_Ref_Data_Loaded table has reference tabledir. This is wrong, because that column sometimes doesn't point to an existing record (so reference integrity sometimes is not maintained for it), for example, in case a module was uninstalled from the system. This in turn means that if a valid .xml file generated through an "export client" execution contains ad_ref_data_loaded records, the process to import it will fail if the data points to non-installed modules, which is not correct. | |||||||||||
Steps To Reproduce | - Create an Openbravo instance. - Import a dataset (for example, the spanish taxes dataset) - Do export client. - Import the client in a different instance. The import process will fail. | |||||||||||
Proposed Solution | The reference of the column should be changed to String. Although this is an API change, it is done to fix an inconsistency, and it's worth to take into account that even if the methods to retrieve the module exist, they would fail in the case a module was uninstalled, so the API was actually "broken". | |||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2012-09-10 17:07 | marvintm | New Issue | ||||||||||
2012-09-10 17:07 | marvintm | Assigned To | => marvintm | |||||||||
2012-09-10 17:07 | marvintm | Modules | => Core | |||||||||
2012-09-10 17:07 | marvintm | OBNetwork customer | => No | |||||||||
2012-09-11 12:36 | AugustoMauch | Relationship added | duplicate of 0021259 | |||||||||
2012-09-11 12:36 | AugustoMauch | Status | new => closed | |||||||||
2012-09-11 12:36 | AugustoMauch | Resolution | open => duplicate |
There are no notes attached to this issue. |