Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0040915 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] Z. Others | minor | have not tried | 2019-05-20 12:58 | 2019-05-20 13:03 | |||||||
Reporter | alostale | View Status | public | |||||||||
Assigned To | Retail | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0040915: retail: review FK columns to set which ones shouldn't generate one-to-many property in parent entity | |||||||||||
Description | After 0040290 implemented the capacity of defining which foreign key database column should generate a one-to-many property in their referenced parent entity, all existing columns were set to continue generating them in order to preserve backward compatibility. All these columns should be now reviewed to decide, case by case, if those parent properties should be generated. | |||||||||||
Steps To Reproduce | - | |||||||||||
Proposed Solution | The following spreadsheet [1], lists all these columns for pi + retail pack. Splitting each of them by the owner team. Column H (Keep) flags whether it should be kept (Y) or can be removed (N). When a column is marked to be removed, SQL column (K) generates the query to be run; grep column (J) contains a grep expression (check comment in header on how to use it) to look for HQL occurrences of the removed property in case there are occurrences (check for false positives), either the column cannot be removed or code needs to be fixed. After executing the SQL, run ant.generate entities and rebuild the system to check for users of the deleted methods. --- [1] https://docs.google.com/spreadsheets/d/1hdwjGM4_3TJ-9Bcylh_w_MM54_1T_cUlicaPfEyH1MQ/edit#gid=0 [^] | |||||||||||
Tags | Performance | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |||||||||||||||
|
Issue History | |||
Date Modified | Username | Field | Change |
2019-05-20 12:58 | alostale | New Issue | |
2019-05-20 12:58 | alostale | Assigned To | => Retail |
2019-05-20 12:58 | alostale | Modules | => Core |
2019-05-20 12:58 | alostale | Triggers an Emergency Pack | => No |
2019-05-20 12:58 | alostale | Issue generated from | 0040906 |
2019-05-20 12:58 | alostale | Relationship added | related to 0040906 |
2019-05-20 12:58 | alostale | Relationship added | depends on 0040290 |
2019-05-20 13:03 | alostale | Tag Attached: Performance |
Copyright © 2000 - 2009 MantisBT Group |