General
All imported and exported data files must reside on the same machine as that serving the database.
You must initialize a database using db-util before importing data.
Proximity automatically converts all attribute names to lower case when importing data; attribute values retain their original case.
Use specialized export functionality available through the Proximity Database Browser to export attribute or NST data to tab-delimited text files.
Delete a database by deleting its files in the
dbfarm directory in your local MonetDB
installation.
XML import and export
The
DTD,
for the XML data format prox3db.dtd, must
reside in the same directory as the import data file.
Copy the DTD file from
$PROX_HOME/resources/ to the directory
containing the data file before importing data.
For compatibility with MonetDB, single quotes, double quotes, and newline characters in the XML data are automatically changed to underscores during import.
The XML data format and associated utilities provide limited error checking against some data corruption problems by restricting the types of data that can be imported into an exiting database.
To override the default restrictions on importing XML data into
existing databases, set the import script noChecks
parameter to true.
Exporting a container to XML exports all the container’s subgraphs, any attributes on those subgraphs, and any containers nested within the specified container, but not the container’s attributes.
Plain text import and export
The plain text data format and associated utilities provide no error checking; you are completely responsible for the consistency and integrity of your imported data.
For compatibility with MonetDB, convert single quotes, double quotes, and newline characters to underscores in a pre-processing step before importing data using the plain text format.
Additional Information
See Appendix C, Proximity XML Format for a description of the XML data format.
See Appendix D, Proximity Text Data Format for a description of the plain text data format.