Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0040290
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminorhave not tried2019-02-28 12:382019-03-13 15:26
ReporteralostaleView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0040290: do not generate one-to-many property in parent entity for all FK properties

DescriptionCurrently, all properties with a FK reference generate a one-to-many reference in the parent entity.

This is the correct behavior in some cases, ie. order.getOrderLineList(), but not in some others, ie. businessParter.getInvoiceList(). Latter case is potentially dangerous as if this method is invoked in a business partner with thousands of invoices, all them will be loaded in memory which can cause an OOM.

Benefits:
  1. Removes potentially dangerous methods, that should never be used
  2. Cleans the model up
  3. Reduces model memory footprint (quick test removing all of them reduced SessionFactory from ~200MB to ~70MB)
  4. Potentially reduces tomcat startup time (needs to be measured)
Steps To Reproduce-
Proposed Solution1. Add a new flag to ad_column to determine whether one-to-many reference should be created

This flag should be defaulted to true for existing columns not to break API, but it should be false for new ones, so those cases are marked only if required.

2. Review existing columns to set the correct value.
TagsPerformance
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to design defect 0029947 acknowledgedplatform Wrong query launched when OBDal.getInstance.getSession.refresh(Object) 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-02-28 12:38 alostale New Issue
2019-02-28 12:38 alostale Assigned To => platform
2019-02-28 12:38 alostale Modules => Core
2019-02-28 12:38 alostale Triggers an Emergency Pack => No
2019-02-28 12:44 alostale Description Updated View Revisions
2019-02-28 12:50 alostale Description Updated View Revisions
2019-02-28 12:51 alostale Relationship added related to 0029947
2019-02-28 12:51 alostale Tag Attached: Performance
2019-03-13 15:26 alostale Status new => acknowledged


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker