Data Import
This function is used to integrate into a folder the data previously extracted with the aid of the extraction utility. The files in question must have been placed beforehand in a sub-directory of the integration folder (SVG by default). It consists of a physical integration (in some ways comparable to an Oracle import: the structure and all the data in the table will be replaced by the contents of the corresponding file, without the possibility to return to the previous position). For each XXX table in the database, four to six files must be present in the directory and these will be read:
a XXX.dat file, which contains the data in the form of a file constructed of fixed length records.
a XXX.srf file, which contains the description of the file structure (ASCII format).
a XXX.fde file, which contains the description of the file structure (in a compiled format directly usable by the Adonix engine: This file also exists in the FIL directory of the folder).
a XXX.blb file, which contains the data linked to the image files (BLOBS) and text files (CLOBS) stored in the table if it has any.
a XXX.seq file, which contains the next sequence number associated with the table. This information is important insofar as each table is associated with a sequence number that makes it possible to create unique numbers (this corresponds to the Adonix function uniqid([abv]), where abv is the table abbreviation).
a XXX.cfg file, which contains the table configuration information in the database. This file is optional, its taking into account depends in addition on the integration options selected. To have more information on the configuration file structure, it is advisable to consult the corresponding technical annex.
Preliminary warning
Warning, this type of function is a maintenance function reserved for developers, it is linked to the Adonix engine and not to the standard databases. As a consequence, it should not be used as a habitual backup procedure, since it does not have the guarantees of security or performance. A backup with the standard database tools is strongly recommended before every use of this type of function.
Screen management
Entry screen
Presentation
The following information is entered in the screen which appears on entering the function:
the folder name (by default the current folder)
the name of the table to be integrated, or a template defining, using wildcard (* and ?) characters, the name of the tables to be integrated.
the directory in which the integration will be carried out (SVG by default, knowing that the value FIL and also the values corresponding to the standard directories - EFRA, TRT, PCD, TXT...- are prohibited). It should be noted that the directory in question is inevitably a sub-directory of the folder. In effect, the valfil integration tool used to do this cannot integrate data on another physical volume to that where the folder directory is found.
a tick box called Original configuration files. When this box is ticked, the file with the extension cfg (if it exists) present in the extraction directory is always ignored, the file that is present in the FIL directory being used if it exists.
a tick box called Original size. When this box is ticked, the sizing information (from the file with the extension srf) found in the integration directory is ignored and instead the information found in the FIL directory (if it exists) is used.
If it is desired for example to integrate all tables in the SVG directory, it is sufficient to enter * in the name of the table.
Validation starts the function, after a confirmation request in a box giving the following message:
| Number of tables to be integrated : NNN |
A log file is created and viewed in order to know the result (and any possible errors in the integration).
Close
Fields
The following fields are present on this tab :
Block number 1
| Define the code of the folder in which the work will be carried out (such as it is defined in the table of the folders). |
| If the folder where the tables are integrated possesses an archive folder, there is the choice to integrate into the archive table (by checking the box) or in the table in the live folder (not checked). |
|
|
| Defines the name of the table to be integrated or a template characterising the name of the tables to be integrated. If for example, all the tables present in the SVG directory are to be integrated, all that is necessary is to enter * in this field. |
Block number 2
| When this box is checked, the file with extension cfg present in the SVG directory is used to define the table, taking into account the configuration directives such as the size of the extents. Its structure is described in an annex. |
| When this box is ticked, the sizing information (from the file with the extension srf) found in the integration directory is ignored and instead the information found in the FIL directory (if it exists) is used. |
Close
Errors in the log file
At the time of the integration, a log file is created. Errors can arise: They appear in the form of an error line (in red) in the log file, followed by additional information.
Tables used
All the dictionary tables holding data are open to being integrated.