QDI Mapping file structure: Difference between revisions
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
|fieldName|| This is the field in the givne table that the values will be mapped to. | |fieldName|| This is the field in the givne table that the values will be mapped to. | ||
|- | |- | ||
|value1|| | |value1||The character offset at which the value will be found in the data file. | ||
|- | |- | ||
|value2|| | |value2||The acceptable length of the field in the data file. | ||
|- | |- | ||
|value3|| | |value3||The field type. | ||
|- | |- | ||
|value4|| | |value4||Denotes whether or not this is the primary key of the table. | ||
|- | |- | ||
|value5|| | |value5|| Default field value. | ||
|- | |- | ||
|} | |} | ||
Revision as of 00:46, 18 January 2006
QDI Mapping file for QESTLab concrete dockets:
Anything preceded by a '#' is a comment, the first few options are as follows:
TABLENAME:DocumentConcreteDockets SYSTEM:QESTLAB DATAFILE:TK*.in TRIMLEADINGZEROS:TRUE
In order these suggest:
- This applies to the DocumentConcreteDockets table
- This mapping file applies to the QESTLab system
- It will read in any files which have a filename of the structure TK*.in where the '*' is a wildcard standing for any string of characters.
- Leading zeros will be trimmed from values.
The rest of the file is structured as follows:
fieldName, value1 , value2, value3 , value4, value5
| Field | Meaning |
| fieldName | This is the field in the givne table that the values will be mapped to. |
| value1 | The character offset at which the value will be found in the data file. |
| value2 | The acceptable length of the field in the data file. |
| value3 | The field type. |
| value4 | Denotes whether or not this is the primary key of the table. |
| value5 | Default field value. |