Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007242Openbravo ERPA. Platformpublic2009-01-29 18:172011-09-21 23:19
Reportershuehner 
Assigned Toshuehner 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionout of date 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version3.0MP0 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0007242: 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.
Additional Information
TagsNo tags attached.
Relationships
related to defect 0005365 closed shuehner Under some circumstances, DataGrid performs two identical queries to retrieve the data 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-01-29 18:17shuehnerNew Issue
2009-01-29 18:17shuehnerAssigned To => shuehner
2009-01-29 18:17shuehnersf_bug_id0 => 2546023
2009-01-29 18:17shuehnerOBNetwork customer => No
2009-01-29 18:17shuehnerRegression testing => No
2009-01-29 18:18shuehnerStatusnew => acknowledged
2009-01-29 18:18shuehnerRelationship addedrelated to 0005365
2011-09-21 23:19shuehnerStatusacknowledged => scheduled
2011-09-21 23:19shuehnerNote Added: 0041221
2011-09-21 23:19shuehnerStatusscheduled => closed
2011-09-21 23:19shuehnerResolutionopen => out of date
2011-09-21 23:19shuehnerFixed in Version => 3.0MP0

Notes
(0041221)
shuehner   
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