Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0023810 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] A. Platform | major | always | 2013-05-13 17:26 | 2014-05-22 06:23 | |||||||
Reporter | egoitz | View Status | public | |||||||||
Assigned To | AugustoMauch | |||||||||||
Priority | urgent | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0023810: The computed columns shouldn't be calculated if the fields is not visible on grid | |||||||||||
Description | The 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 | |||||||||||
Tags | Performance | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0058633) alostale (manager) 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. |
Issue History | |||
Date Modified | Username | Field | Change |
2013-05-13 17:26 | egoitz | New Issue | |
2013-05-13 17:26 | egoitz | Assigned To | => AugustoMauch |
2013-05-13 17:26 | egoitz | Modules | => Core |
2013-05-13 17:26 | egoitz | Triggers an Emergency Pack | => No |
2013-05-13 17:27 | egoitz | Tag Attached: Performance | |
2013-05-14 11:15 | alostale | Note Added: 0058633 | |
2013-05-14 11:15 | alostale | Type | defect => design defect |
2014-05-22 06:23 | eintelau | Issue Monitored: eintelau |
Copyright © 2000 - 2009 MantisBT Group |