Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0032201 | Openbravo ERP | A. Platform | public | 2016-02-11 11:41 | 2016-02-25 15:08 |
|
Reporter | AtulOpenbravo | |
Assigned To | platform | |
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0032201: Unnescessary performance penalty while sorting and filtering column of HQL Datasources used in P&E windows |
Description | In 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 Reproduce | In 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. |
Proposed Solution | |
Additional Information | |
Tags | Performance |
Relationships | related to | defect | 0032157 | | closed | AtulOpenbravo | Not possible to sort by unit price in Return from Customer p&e | related to | defect | 0032344 | | acknowledged | Triage Platform Base | HQL based tables don't can produce incorrect pagination |
|
Attached Files | |
|
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 |
Notes |
|
|
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 |
|
|
|
The problem is not what this issue reports, but that sometimes id column is not added to the fetch query, see issue 0032344 |
|