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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0007242
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformmajorhave not tried2009-01-29 18:172011-09-21 23:19
ReportershuehnerView Statuspublic 
Assigned Toshuehner 
PrioritynormalResolutionout of dateFixed in Version3.0MP0
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0007242: Optimize DataGrid fetch logic to use one bigger request instead of two distinct small request

DescriptionThe current datagrid does request two, non-overlapping ranges of the data. Using a single bigger fetch request could/will lead to improved performance.

Steps To ReproduceGo to the Business Partner selector
Resize the window that only two lines are shown
Position the marker/cursor on the first line
Open a Firebug or a similar tool to log the requests sent to the server
Press the "end" key on the keyboard do directly go to the last line
- See that two requests and sent to the Server.
  - Check the post parameter for the two requests
  - See the the offset,page_size of the requests
    specify two non-overlapping regions around the currently selected
    (target) line.
Proposed SolutionOptimize the code in the datagrid.js file to issue one combined fetch request which does request on region containing both needed ranges.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0005365 closedshuehner Under some circumstances, DataGrid performs two identical queries to retrieve the data 

-  Notes
(0041221)
shuehner (administrator)
2011-09-21 23:19

With the new 3.0 major version the grid code was completely rewritten and does not have the old problem anymore of loading data in two parts. Marking as out-of-date

- Issue History
Date Modified Username Field Change
2009-01-29 18:17 shuehner New Issue
2009-01-29 18:17 shuehner Assigned To => shuehner
2009-01-29 18:17 shuehner sf_bug_id 0 => 2546023
2009-01-29 18:17 shuehner Regression testing => No
2009-01-29 18:18 shuehner Status new => acknowledged
2009-01-29 18:18 shuehner Relationship added related to 0005365
2011-09-21 23:19 shuehner Status acknowledged => scheduled
2011-09-21 23:19 shuehner Note Added: 0041221
2011-09-21 23:19 shuehner Status scheduled => closed
2011-09-21 23:19 shuehner Resolution open => out of date
2011-09-21 23:19 shuehner Fixed in Version => 3.0MP0


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker