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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0043416
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 04. Warehouse managementminorhave not tried2020-03-04 14:342020-03-04 14:35
ReportershuehnerView Statuspublic 
Assigned ToTriage Omni WMS 
PrioritynormalResolutionopenFixed in Version
StatusnewFix 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

0043416: PL-function m_get_product_cost could be made 2 * faster

DescriptionThis pl-function checks twice in m_costing table:
a.) First to see if there are any rows in the matching range
b.) Then querying again to fetch the first interesting rows.

In practice that doubles runtime compared to only doing a single query.

Attached files (of OLD 2.50 version of the pl) show idea of this change.

Pending to check:
1.) The date filters are not identical between the 2 checks. The 'BETWEEN' usage filters for <= DATETO while the fetching query does < DATETO
That should be still fine as the 'shortcut count(*) is less restrictive' so the 2nd query should still return the correct result

2.) Recent change added extra filter condition:
17092: AND costtype NOT IN ('AVA' , 'STA')
to make it 'not costing new engine costs'.
That should be probably added instead to the 2nd query

3.) That change 17092 is unclear if totally correct today. While it does exclude AVA,STA from the shortcut query it will not filter those out when retrieving data.

Steps To Reproduce-
TagsNo tags attached.
Attached Files? file icon m_get_product_cost-original.sql [^] (2,725 bytes) 2020-03-04 14:34
? file icon m_get_product_cost-new.sql [^] (2,457 bytes) 2020-03-04 14:34

- Relationships Relation Graph ] Dependency Graph ]
related to design defect 0022417 newTriage Omni OMS The Pareto Product Legacy reports takes long to show a big amount of data 

-  Notes
(0118322)
shuehner (administrator)
2020-03-04 14:35

Note: Issue is mostly reported to see if that improvement is still relevant / interesting with current 3.0 code.

- Issue History
Date Modified Username Field Change
2020-03-04 14:34 shuehner New Issue
2020-03-04 14:34 shuehner Assigned To => Triage Finance
2020-03-04 14:34 shuehner Modules => Core
2020-03-04 14:34 shuehner Triggers an Emergency Pack => No
2020-03-04 14:34 shuehner File Added: m_get_product_cost-original.sql
2020-03-04 14:34 shuehner File Added: m_get_product_cost-new.sql
2020-03-04 14:35 shuehner Note Added: 0118322
2020-03-04 18:17 shuehner Relationship added related to 0022417


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker