Framework:Tables
The data entered by the user are saved in tables. The user may enter data in tables by means of input masks. In order to process a table, highlight it and press the “design” button or select “design” from the context menu (can be called up by pressing the right mouse button). Double-clicking on the table will also open it in design view.
The table designer opens:
Table designer
It consists of three areas:
- the tabs
- the tab area
- the general area
General area
There are five buttons, and their function is as follows:
OK Applies the modifications and closes the table designer. Update table If the table does not yet exist, “Update table” creates it. New fields, which are subsequently available, are created in the database. For dimensions, default elements (root element and “No assignment” element) are created. “Update table” carries out the following steps: • The definition of the table is saved • All fields that are enabled (-> red triangle, these fields are not yet in the data table and can be processed without restriction up to this stage!) are now applied in the data table (also in database!) and cannot be renamed from now on!(-> because there is no consistency of the corresponding DB commands across different databases!) • Other settings of fields that do not effect a change in the database can still be processed, as they are made when the table is “loaded”! • Table is reloaded on the server (see “Apply“) • The data of the data table remain unaffected! • Deleted columns will only be removed from the database when updating is performed! Apply “Apply” saves the current definition – tables are not re-created in the database. Newly calculated fields are available immediately. Note Saves the definition of the table on the CoPlanner server; but does not apply these changes in the real data table on the database server! Green-ticked fields have already been applied in the data table (with “Update table”!), fields with the red triangle have not been applied in the data table! An exception are calculated fields, which are also applied in the data table with “Apply”. This is because calculated fields are not saved in the database. Instead, they are added by the CoPlanner server and only available in the memory (in the server cache)! The following steps are carried out: • The definition of the table is saved • The table is reloaded from the relational database to the CoPlanner server (as it is!) • Table is revised with information from the table definition (e.g.: calculated fields are added!) • Changes in the definition that require a re-creation of the data table in the database are not performed! (-> red triangle!) • The data of the data table remain untouched! Re-create table The table is re-created in the database. Note Caution – this deletes all existing data!!! “Re-create table” carries out the following steps: • The existing data table is deleted! • The data table is re-created, as if a new table was created manually! • This means that the new table now consists of system columns only! • The table is reloaded on the server (see above!) • The fields saved in the definition are now enabled again as they are not in the data table! They can now be processed, and the table can then be rebuilt with these fields ->“Update table“ • The data of the data table are lost! Cancel Nothing is saved and the window is closed. 5.2.2 Fields Here we are in the “Fields” tab. To create a new field, click on the “Add field” button.
