The loader objectName of the loader object. The loader object uniquely identifies a loader process and stores all export settings entered into the form. Thus you can combine repeatedly used export activities in loader objects and manage them in the database. |
|
The loader fileName of the loader file. attribute master
attribute for loader object (T_LOAD) For exorting you enter any loader file name (*.bin)
including (server!)-path (selection via file browser only possible if
DataView server and client run on the same host computer). Default path
and file name are... The file created by the new loader is a binary file and, thus, not editable. In addition to the records to be exported, the loader file stores all information defining the export precess in detail (exported tables, selection criteria, field pre-assignments). For importing you enter the name of an existing loader file (*.bin) including (server!)-path (selection via file browser or using drag&drop only possible if DataView server and client run on the same host computer). Default path and file name are....application_dir\dmp\export.bin. DataView will then ask you if you want to use the content of the loader file. Type "yes" and all information stored in the loader file (exported tables, selection criteria, field pre-assignments) is read and displayed in the corresponding form fields. In case you want to skip the question pop-up window, you need to change the settings for the default LOA-REA-ALWAYS as follows: type=S and value=true. With these settings the loader file, if existing, is always read immediately without asking. |
|
The log file Name of the log file. attribute master
attribute for loader object (T_LOAD) All activities executed by DataView in an import or export procedure can be additionally recorded in a log file. The log file is in readable ASCII format and can be opened with any editor. It lists the C_IDs of all exported/imported records as well as the corresponding table names. For exporting and importing you enter any log file name *.log including (server!)-path (selection via file browser only possible if DataView server and client run on the same host computer). Default path and file name are ... application_dir\tmp\export.log. |
|
Comment Comment on the loader object. attribute master
attribute for loader object (T_LOAD) |
|
Table name List of the table to be exported attribute relation
attribute for loader object-table (T_LOA_TAB) For exporting you enter all the tables into this list whose data you want to export. Selection is done using a choice box. It offers all DataView system tables for exporting meta data of an application as well as all database tables created for the application for exporting user data stock. |
|
![]() |
Always export all tables that are related in the data model. Thus you make sure that all internal references in the data model are also contained in the loader file! |
During export immediately after selecting the loader file, the list displays all tables whose names were exported in the loader file. | |
Example: You have added or customized a number of fields in a development environment and want to port these changes to a test system or a productive system. To do so, you have to select all DataView system tables relevant for the definition of the field objects. These are T_FIELD, T_MASK, T_MAS_FLD, T_TABLE, T_TAB_FLD. As selection criteria you must enter the following terms. We assume that the field name MED_% identifies the changed fields. T_FIELD.C_NAME
| MED_% |
|
Field name Table fiels to limit the export/import functions. type, entry string, uppercase, specification optional
Depending on the tables to be exported, the choice box at the field offers all fields available for defining selection criteria. This results in different opportunities to limit export or import to certain data: DataView system fields global DataView system fields for each individual table
Application-specific attribute fields Joins for each individual table |
|
![]() |
Attention! Tables containing a BLOB field can not be exported as dependent tables with the binary loader (link via "parenttable-<JOIN" or "parenttable-<CONST"). Currently this behavior cannot be changed. |
The desired search terms and join tables for each field you must define in the -> query expression field. Search terms and join conditions for several fields are AND-combined. During import immediately after selecting the loader file and answering "yes" at the pop-up window about the file content, the list displays all tables whose names were defined during export. In case of logical import via import/replace the selection criteria displayed are responsible for deleting records in the target system. Immediately before starting the import process you can change or extend the criteria for this load mode. For all other logical load modes and for direct import changes to the displayed selection criteria are without any effect. Example: You have added or customized a number of fields in a development environment and want to port these changes to a test system or a productive system. To do so, you have to select in -> table name all DataView system tables relevant for the definition of the field objects. These are T_FIELD, T_MASK, T_MAS_FLD, T_TABLE, T_TAB_FLD. As selection criteria you must enter the following terms. We assume that the field name MED_% identifies the changed fields. T_FIELD.C_NAME | MED_% |
|
Query Expression Search terms to limit the export/import of records. type, entry string,
entry optional You enter search terms and join tables for the table fields, are selected in the field -> field name: For DataView system fields and application-specific
attribute fields For individual table joins Search terms and join conditions for several fields are AND-combined. During import immediately after selecting the loader file and answering "yes" at the pop-up window about the file content, the list displays all tables whose names were defined during export. In case of logical import via import/replace the selection criteria displayed are responsible for deleting records in the target system. Immediately before starting the import process you can change or extend the criteria for this load mode. For all other logical load modes and for direct import changes to the displayed selection criteria are without any effect. Example: You have added or customized a number of fields in a development environment and want to port these changes to a test system or a productive system. To do so, you have to select in -> table name all DataView system tables relevant for the definition of the field objects. These are T_FIELD, T_MASK, T_MAS_FLD, T_TABLE, T_TAB_FLD. As selection criteria you must enter the following terms. We assume that the field name MED_% identifies the changed fields. T_FIELD.C_NAME | MED_% |
|
Field Name Table fields for automatic pre-assignment |
|
type, entry string, uppercase, specification
optional max. no. of characters 50 selection tool Menü mit den Feldern aller für den Loadervorgang ausgewählten Datenbank-Tabellen, geordnet nach internen Systemfeldern und objektspezifischen Attributfeldern multilingual field no Depending on the tables to be exported, the choice box at the field offers all fields available for automatic pre-assignment. This results in different opportunities to pre-assign fields: DataView system fields global DataView system fields for each individual table Application-specific attribute fields The desired values for automatic pre-assignmentand you must enter in the -> text entry field. The values must be type compatible. You can define an automatic pre-assignment of fields for export or import (direct import and all modes of the logical import), depending on whether the loader files already contain the pre-assignment. |
|
Text Entry Values for automatic pre-assignment of table
fields. You enter values for the table fields, are selected in the field -> field name. The values must be type compatible. |
|
![]() |
The pre-assignment of date fields must be done using the database date format YYYY-MM-DD HH:MM:SS. |
You can define an automatic pre-assignment of fields for export or import (direct import and all modes of the logical import), depending on whether the loader files already contain the pre-assignment. | |
Transaction Clause On/OFF Combines single statements to one database transaction. In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause. It combines single statements to one transaction. Please note that a complete rollback of an import of a large loader file with several thousand records is only possible if the rollback segment of the database is sufficiently large. |