Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0023810Openbravo ERPA. Platformpublic2013-05-13 17:262014-05-22 06:23
Reporteregoitz 
Assigned ToAugustoMauch 
PriorityurgentSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0023810: The computed columns shouldn't be calculated if the fields is not visible on grid
DescriptionThe computed columns shouldn't be calculated if the fields is not visible on grid.
If not possible shouldn't be calculated if the column is deactivated
Steps To Reproduce-Put a computed column on sales order window as not visble on grid.
-compile and restart
-Access the application
-go to sales order window
-See that the select executed calculates the computed columns.

*The same happens deactivating the column
Proposed Solution
Additional Information
TagsPerformance
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-05-13 17:26egoitzNew Issue
2013-05-13 17:26egoitzAssigned To => AugustoMauch
2013-05-13 17:26egoitzModules => Core
2013-05-13 17:26egoitzTriggers an Emergency Pack => No
2013-05-13 17:27egoitzTag Attached: Performance
2013-05-14 11:15alostaleNote Added: 0058633
2013-05-14 11:15alostaleTypedefect => design defect
2014-05-22 06:23eintelauIssue Monitored: eintelau

Notes
(0058633)
alostale   
2013-05-14 11:15   
Updating to design defect.

Two design defects are affecting in this case:

1- Grid datasource returns values for all column in the entity regardless they're shown in grid.
2- Computed columns are calculated when the DAL record is obtained. They should be calculated lazily when they're going to be used. This needs to be checked on how affects performance in case they are used, because this would require to compute them record by record rather than all at once.

Doing these change require redesigning some core components. Note 2nd one to be useful depends on 1st one to be implemented.