|
VADELIA |
|
WADELIA |
|
(I) (C/S) |
(I) (C/S) |
Section for use
DECLARATION
Syntax
LOADING Id ObjectName AccessDef Step Add OptimizeRows
ObjectName |
→ |
List property for a graphic object, in the form |
"Window.GraphicObjectName:Property" |
||
AccessDef |
→ |
*EQUAL_KEY EntityAccJoin AccessField |
| *SEQ_KEY EntityAccJoin AccessField |
||
| *PRV_EQL_KEY EntityAccJoin AccessField |
||
| *START_WITH EntityAccJoin AccessField |
||
| *PRV_READ EntityAccJoin AccessField |
||
| *DIRECT EntityAccJoin NumericVarId |
||
| *SEQ_NO_KEY EntityAccJoin |
||
| *SQL SeriesEntities Distinct SelectedColumns AdeliaCond SortOption |
||
| *SQL_D DynQuery SeriesHostFields |
AccessField |
→ |
AccessField, VarId | VarId |
SeriesEntities |
→ |
SeriesEntities, Entity | Entity |
Distinct |
→ |
*DISTINCT | None |
SelectedColumns |
→ |
*COL(SeriesEntityFields) | None |
SeriesEntityFields |
→ |
SeriesEntityFields, EntityVarId | EntityVarId |
SeriesEntities |
→ | SeriesEntities, Entity | Entity |
Entity |
→ |
EntityName CorrelationName |
| EntityName |
SeriesHostFields |
→ |
SeriesHostFields HostField | HostField |
HostField |
→ |
VarId | VarId | IndicVarId |
Step |
→ |
Integer |*STEP(Integer) | *STEP(IdVar) | *STEP(*AUTO) | None |
Add |
→ |
*ADD | *ADD(ProcedureName) | None |
OptimizeRows |
*OPT(n) | None |
DynQuery |
→ |
AlphaVarId | SQLStatementName |
Description
Declaration of a type of graphic list loading named Id , which loads the list for the graphic object ObjectName from an entity, access or join entity EntityAccJoin , with the access definition AccessDef and the fields making up the key AccessField . Loading takes place Step records at a time.
With loadings of types *EQUAL_KEY, *SEQ_KEY, *PRV_EQL_KEY, *START_WITH and *PRV_READ, you must specify the fields forming the access.
With *DIRECT loadings, you have to give the name of the numeric variable to be used as the relative record number.
With *SEQ_NO_KEY loadings, there is no key to specify.
With *SQL loadings, you have to enter the names of the entities concerned, the read condition and the sorting key. The condition and sorting key are optional. All fields in the entities will receive the values from the database.
Click here for the explanation of the SortOption element.
By default, the instruction returns the values of all the entities' columns.
However, it is possible to retrieve only the values which are specified in SelectedColumns.
When *DISTINCT is specified, only the distinct rows are returned (considering all the columns or the columns selected in SelectedColumns).
With *SQL_D loadings, you must enter either the name of the alphanumeric variable or the name of the SQL statement declared beforehand via the SQL_STATEMENT instruction, which contains the SQL query to be applied, followed by the series of fields that are to receive the values from the database.
Warning: In the SQL query contained in the variable, you have to give the real name of the columns and arrays, not their Adelia names.
The Step can be specified using an integer constant or the strictly positive value contained in an integer numerical variable. If you specify the *AUTO value for Step , the loading step is deduced from the GRAPHICAL_STEP property of the object concerned by the loading. The *AUTO value is only allowed for objects with the GRAPHICAL_STEP property. If the Step is not set to a specific value, the loading will be static.
In the case of graphic list updates, you can specify the name of the procedure that will add extra rows that are different from the default rows. In the default rows, alphanumeric fields are left blank and numeric fields are set to zero. The loading procedure is determined by Add .
Add can only be used if a Step has been specified.
With *SQL or *SQL_D loadings, it is possible to ask the SQL optimizer to optimize query execution so as to retrieve the first x rows of the cursor more quickly (*OPT parameter). By default, a loading with a Step specified by an integer constant operates with an optimization clause corresponding to the loading step. You can prevent Adelia from generating the optimization clause by setting the *OPT parameter to *OPT(0).
Notes:
- The accesses *EQUAL_KEY, *SEQ_ KEY, *PRV_EQL_KEY, *START_WITH, *PRV_READ, *DIRECT, *SEQ_NO_KEY can only be used with databases accepting such file accesses.
- *DIRECT access is impossible for BTrieve databases.
- *SQL and *SQL_D accesses can only be used with databases that accept SQL accesses.
Click here for the explanation on the Adelia condition element.
Example
LOADING Load1 WIN1.ZLIST:LIST *EQUAL_KEY |
CUSTOMER CUST_CODE, CUST_NAME 5 |
LOADING Load2 WIN1.ZLIST:LIST *SEQ_KEY |
CUSTOMER CUST_CODE, CUST_NAME |
LOADING Load3 WIN1.ZLIST:LIST *PRV_EQUAL_KEY |
CUSTOMER CUST_CODE, CUST_NAME |
LOADING Load4 WIN1.ZLIST:LIST *DIRECT |
CUSTOMER RANK *ADD |
LOADING Load5 WIN1.ZLIST:LIST *START_WITH |
CUSTOMER CUST_CODE, CUST_NAME |
LOADING Load6 WIN1.ZLIST:LIST *SEQ_NO_KEY |
CUSTOMER |
LOADING Load7 WIN1.ZLIST:LIST *PRV_READ |
CUSTOMER CUST_CODE, CUST_NAME |
LOADING Load8 WIN1.ZLIST:LIST *SQL_D Query |
CUST_CODE CUST_NAME 10 *ADD(PROC1) |
LOADING Load9 WIN1.ZLIST:LIST *SQL ORDER |
*COND(CCUST_CODE = :ZCUST_CODE) - |
*SORT(OODR_NUM) |
|
LOADING LOAD_PRODUCT1 SEL_PROD_WIN.LST_PROD:LIST *SQL PRODUCT *COND(PCPY_COD - |
|
LOADING LOAD_PRODUCT2 SEL_AGREE_WIN.COMBO_LST_PRO:LIST *SQL PRODUCT *COND - |
|
LOADING LOAD_INVOICE_CLI CLILST:LIST *SQL CLIENT, HEADER_INV - *COND(CL_CLI_CODE = CLI_CODE_INV) *SORT (CL_CLI_NAME) 10 *ADD |
|