Project:
| View Revisions: Issue #40290 | [ Back to Issue ] | ||
| Summary | 0040290: do not generate one-to-many property in parent entity for all FK properties | ||
| Revision | 2019-05-10 10:27 by alostale | ||
| Description | See project specs [1]. Currently, 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) --- [1] http://wiki.openbravo.com/wiki/Projects:Configurable_Child_OneToMany_Property_In_Parent_Entity [^] |
||
| Revision | 2019-02-28 12:50 by alostale | ||
| Description | Currently, 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) |
||
| Revision | 2019-02-28 12:44 by alostale | ||
| Description | Currently, 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 4. Potentially reduces tomcat startup time (needs to be measured) |
||
| Revision | 2019-02-28 12:38 by alostale | ||
| Description | Currently, 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. Additionally this pollutes the model (and makes it slower to load? -needs to be measured-) |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |