Differences

This shows you the differences between two versions of the page.

--- visionx:data_modeling_and_representation [2020/06/10 10:43]
cduncan
+++ visionx:data_modeling_and_representation [2024/11/18 10:40] (current)
admin
@@ Line 2: / Line 2: @@
 ~~Title: Data Modeling and Representation~~
-Version: 1.0 / 2019-07-01
+Version: 1.1 / 2024-11-18
 ====== Introduction ======
@@ Line 90: / Line 90: @@
 {{:visionx:data_modeling_and_representation:drop_down_combo_swing.png?nolink|Drop-down no foreign-key relation: Result desktop}}
-Just in case you want to know how this works: [[:jvx:client:model:databook:autolistboxes|JVX offers a a simple solution for linking tables]] called "Automatic Link Reference". For every database table (or view) you access from within your screen, a so-called "Storage" is created in the screen's server-class.
+Just in case you want to know how this works: [[:jvx:client:model:databook:autolistboxes|JVx offers a a simple solution for linking tables]] called "Automatic Link Reference". For every database table (or view) you access from within your screen, a so-called "Storage" is created in the screen's server-class.
 With our [[:visionx:eplug_guide|EPlug Plugin]], you can jump to the storage's source code in Eclipse by opening the Configure Server-Side Data Storages Wizard (1) and pressing "Show Source code" (2).
@@ Line 141: / Line 141: @@
 ==== Restrict Content of Dropdown List ====
-Of course, JVX offers many more features to enhance our application without manipulating the data model. For example, we assume that the manager of each department must be assigned to the department he or she manages. Therfore, we may want to restrict the employees in the manager listbox to employees which are assigned to the corresponding department.
+Of course, JVx offers many more features to enhance our application without manipulating the data model. For example, we assume that the manager of each department must be assigned to the department he or she manages. Therfore, we may want to restrict the employees in the manager listbox to employees which are assigned to the corresponding department.
 With our [[:visionx:eplug_guide|EPlug Plugin]], you can jump to the editor's client source code in Eclipse by selecting the editor and pressing the eclipse icon (1).
@@ Line 147: / Line 147: @@
 {{:visionx:data_modeling_and_representation:drop_down_eplug_editor.png?nolink|Drop-down no foreign-key relation: EPlug jump to editor}}
-In JVX, the dropdown list is an [[http://www.sibvisions.com/files/jvx/current/api/index.html?javax/rad/ui/celleditor/ILinkedCellEditor.html|ILinkedCellEditor]]. We restrict the data in the dropdown list by setting an additional condition to the cell editor:
+In JVx, the dropdown list is an [[http://www.sibvisions.com/files/jvx/current/api/index.html?jvx/rad/ui/celleditor/ILinkedCellEditor.html|ILinkedCellEditor]]. We restrict the data in the dropdown list by setting an additional condition to the cell editor:
 <code java>
@@ Line 201: / Line 201: @@
 {{:visionx:data_modeling_and_representation:subtable_step4.png?nolink|Subtable one-to-many: Data model}}
-But a clean one-to-many relation in the data model does not fully do the trick. We want each record of EMPLOYEES to be linked to its records in ASSETS, so that whenever we select an employee (only) the assets assigned to that employee are shown. In JVX, this kind of link between table and subtable is called "Master Reference": the subtable only shows records linked to the currently selected record in the master table. When we created the subtable via VisionX, the "Master Reference" was set automatically. In the data-object wizard of the subtable ASSETS, the table EMPLOYEES is specified as master table:
+But a clean one-to-many relation in the data model does not fully do the trick. We want each record of EMPLOYEES to be linked to its records in ASSETS, so that whenever we select an employee (only) the assets assigned to that employee are shown. In JVx, this kind of link between table and subtable is called "Master Reference": the subtable only shows records linked to the currently selected record in the master table. When we created the subtable via VisionX, the "Master Reference" was set automatically. In the data-object wizard of the subtable ASSETS, the table EMPLOYEES is specified as master table:
 {{:visionx:data_modeling_and_representation:subtable_step4_master.png?nolink|Subtable one-to-many: Master reference}}
@@ Line 231: / Line 231: @@
     }
 </code>
-> **See**: More information on the [[http://www.sibvisions.com/files/jvx/current/api/index.html?javax/rad/model/reference/ReferenceDefinition.html|ReferenceDefinition of a Master Reference]] is available in the documentation of the JVX API.
+> **See**: More information on the [[http://www.sibvisions.com/files/jvx/current/api/index.html?jvx/rad/model/reference/ReferenceDefinition.html|ReferenceDefinition of a Master Reference]] is available in the documentation of the JVx API.
 After populating the ASSETS table using the script [[https://doc.sibvisions.com/_media/visionx/data_modeling_and_representation/hr_popul_4.sql|hr_popul_4.sql]], your extended web application may now look like this now:
@@ Line 507: / Line 507: @@
 ===== Filters Use IConditions =====
-How does this work? Each filter editor creates an [[http://www.sibvisions.com/files/jvx/current/api/index.html?javax/rad/model/condition/ICondition.html|ICondition]] and is connected to other conditions by the logical operator AND. In other words, if multiple filters are set, the result contains only those rows that match all of the filters.
+How does this work? Each filter editor creates an [[http://www.sibvisions.com/files/jvx/current/api/index.html?jvx/rad/model/condition/ICondition.html|ICondition]] and is connected to other conditions by the logical operator AND. In other words, if multiple filters are set, the result contains only those rows that match all of the filters.
 Of course, VisionX supports more than one search mode to use in filters and conditions. These are:
@@ Line 530: / Line 530: @@
 |**Full text search**|Matches all literals that contain the entered value in any column. <html><br></html>Supports ?, * and % as wildcards.|
-The "full text search filter" operates on all columns of the data object.
+The "Full text search filter" operates on all columns of the data object.
 ===== Specify a BETWEEN Filter =====