Project:
| View Revisions: Issue #26267 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0026267: Re-implement combos (table and tableDir) to use datasources | ||
| Revision | 2014-04-14 08:40 by alostale | ||
| Description | Currently, in Openbravo 3 there are two fundamental ways to define a Foreign key column: * Using a selector (the "Defined selector" reference) * Using an old-schooled combo (the "table", or "tableDir" reference). Selectors use OB3 Smartclient components, and are attached to a datasource. Combos also use Smartclient components in OB3, but instead of being attached to a datasource, they are filled with the whole set of data using the OB 2.50 ComboTableData classes. So combos currently have a main performance disadvantage: Current combos have quite good performance if the dataset they query is small, but scale poorly, and if the dataset is big enough, they have terrible performance, and they can even drag down the application for all users. |
||
| Revision | 2014-04-14 08:39 by alostale | ||
| Description | Currently, in Openbravo 3 there are two fundamental ways to define a Foreign key column: * Using a selector (the "Defined selector" reference) * Using an old-schooled combo (the "table", or "tableDir" reference). Selectors use OB3 Smartclient components, and are attached to a datasource. Combos also use Smartclient components in OB3, but instead of being attached to a datasource, they are filled with the whole set of data using the OB 2.50 ComboTableData classes. So combos currently have a main disadvantages: * '''Performance''': Current combos have quite good performance if the dataset they query is small, but scale poorly, and if the dataset is big enough, they have terrible performance, and they can even drag down the application for all users. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |