Export > Text export > Schema File

Associated Schema file

When text exporting from PdxEditor (*.txt, *.csv or *.tab) every export by default will be accompanied by a *.sch schema file describing the data type nature of the exported data.

The schema file is of the semicolon separated delimited nature with the following structure:

"DataType";"Size";"FieldName"

which for the DBDemos biolife.dbf table would be:

"DataType";"Size";"FieldName"
"FLOAT";"0";"SPECIES_NO"
"VARCHAR";"15";"CATEGORY"
"VARCHAR";"30";"COMMON_NAM"
"VARCHAR";"40";"SPECIES_NA"
etc. ...

or for the original Paradox version biolife.db table:

"DataType";"Size";"FieldName"
"FLOAT";"0";"Species No"
"VARCHAR";"15";"Category"
"VARCHAR";"30";"Common_Name"
"VARCHAR";"40";"Species Name"
etc. ...

Please note that several of the exported field types do not have a specified size - PdxEditor exports numeric fields as the cross format generic numeric types not being specified by size which is in contrast to the dBASE text formatted numeric types. In contrast to especially the dBASE table types field sizing is mainly pertinent to the string type fields.

The Schema file structure across systems

Schema files are much used when exporting/importing data between various data systems.
However, structure of Schema files is not standardized, though the information is easily readable and usually easy to adapt to even very large numbers of data to comply with the local importing database application.

Though database schemas often do include information about the CodePage associated with exported text data, this has been omitted from the PdxEditor schema files in favour of the specific UTF-8 Unicode encoding including byte order mark (BOM) for proper decoding - for export targeted e.g. the MySQL database the BOM may be deselected by the user from the Export menu.
Please see Character set encoding.
Please see CSV-import screen.