Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
| View Issue Details | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
| 0035629 | Openbravo ERP | A. Platform | public | 2017-03-28 10:24 | 2022-02-01 08:09 | |||||||
| Reporter | alostale | |||||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | |||||||
| Status | acknowledged | Resolution | open | |||||||||
| Platform | OS | 5 | OS Version | |||||||||
| Product Version | ||||||||||||
| Target Version | Fixed in Version | |||||||||||
| Merge Request Status | ||||||||||||
| Review Assigned To | ||||||||||||
| OBNetwork customer | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Support ticket | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0035629: add per DB object info to check for model DB changes | |||||||||||
| Description | Before updating database, a check to ensure there are no local modification is performed. It checks the model by creating a CRC of the all DB objects. Currently this information is saved only as an aggregation, but it is not possible to know individual objects CRC. This causes: - When there is a model change, it is not possible to know which objects were modified. - When there is need to debug what's happening (ie. 0035628) it's hard. | |||||||||||
| Steps To Reproduce | - | |||||||||||
| Proposed Solution | Save CRC of individual objects and use it to report what changed. Attached a debugging code doing it. | |||||||||||
| Additional Information | ||||||||||||
| Tags | No tags attached. | |||||||||||
| Relationships |
| |||||||||||
| Attached Files |  db_modified-issue.diff (6,362) 2017-03-28 10:24https://issues.openbravo.com/file_download.php?file_id=10611&type=bug | |||||||||||
| Issue History | ||||||||||||
| Date Modified | Username | Field | Change | |||||||||
| 2017-03-28 10:24 | alostale | New Issue | ||||||||||
| 2017-03-28 10:24 | alostale | Assigned To | => platform | |||||||||
| 2017-03-28 10:24 | alostale | Modules | => Core | |||||||||
| 2017-03-28 10:24 | alostale | Triggers an Emergency Pack | => No | |||||||||
| 2017-03-28 10:24 | alostale | Relationship added | related to 0035628 | |||||||||
| 2017-03-28 10:24 | alostale | File Added: db_modified-issue.diff | ||||||||||
| 2017-03-28 10:25 | alostale | Proposed Solution updated | ||||||||||
| 2017-03-28 10:30 | alostale | Status | new => acknowledged | |||||||||
| 2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base | |||||||||
| There are no notes attached to this issue. |