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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0032201
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2016-02-11 11:412016-02-25 15:08
ReporterAtulOpenbravoView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix 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

0032201: Unnescessary performance penalty while sorting and filtering column of HQL Datasources used in P&E windows

DescriptionIn case of sort or filter applied in foreign key column of HQL Datasource used in P&E window raises unnecessary performance penalty and that affects all the P&E windows. In "Return To Vendor" or "Return From Customer" window when sorting / filtering Return Reason column separate left clauses needs to be implemented in order to handle both ID and first IDENTIFIER column from the entity, filter by id and sort by first identifier column.
Steps To ReproduceIn case of sort or filter applied in foreign key column of HQL Datasource used in P&E window raises unnecessary performance penalty and that affects all the P&E windows.In "Return To Vendor" or "Return From Customer" window when sorting / filtering Return Reason column separate left clauses needs to be implemented in order to handle both ID and first IDENTIFIER column from the entity, filter by id and sort by first identifier column.
TagsPerformance
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0032157 closedAtulOpenbravo Not possible to sort by unit price in Return from Customer p&e 
related to defect 0032344 acknowledgedTriage Platform Base HQL based tables don't can produce incorrect pagination 

-  Notes
(0084100)
vmromanos (manager)
2016-02-11 11:58

Order by clause when we open the P&E for the first time:

ORDER BY obSelected desc, obSelected desc, io.movementDate desc, io.documentNo desc, iol.lineNo



Order by clause when we order by any of the columns, for example the name (notice the final iol.id):

ORDER BY obSelected desc, iol.product.name desc , iol.id
(0084513)
alostale (manager)
2016-02-25 15:08

The problem is not what this issue reports, but that sometimes id column is not added to the fetch query, see issue 0032344

- Issue History
Date Modified Username Field Change
2016-02-11 11:41 AtulOpenbravo New Issue
2016-02-11 11:41 AtulOpenbravo Assigned To => platform
2016-02-11 11:41 AtulOpenbravo Modules => Core
2016-02-11 11:41 AtulOpenbravo Triggers an Emergency Pack => No
2016-02-11 11:58 vmromanos Note Added: 0084100
2016-02-11 12:01 vmromanos Relationship added related to 0032157
2016-02-11 12:03 vmromanos Tag Attached: Performance
2016-02-25 15:07 alostale Relationship added related to 0032344
2016-02-25 15:08 alostale Note Added: 0084513
2016-02-25 15:08 alostale Status new => closed
2016-02-25 15:08 alostale Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker