Import XML file to server
Reads an XML file into an edmModel in a remote EDMdatabase. The main features of the command are:
- If the model does not exist, it is implicitly created.
- The XML data may overwrite an existing population or it may increment it.
Arguments:
Server context name: |
Specify name of server context. |
Remote repository: |
The name of the edmRepository in which to create and/or populate an edmModel with the XML data stored in the file specified by the <xmlFileName> argument. The edmRepository specified by this argument must exist in the remote EDMdatabase. Repository names are case sensitive. |
Remote model: |
The name of the edmModel to create and/or populate. The <remoteRepositoryName> and <remoteModelName> arguments uniquely identify an existing edmModel in the remote EDMdatabase. Model names are case sensitive. |
Remote header model repository: |
Not yet implemented. |
Remote header model: |
Not yet implemented. |
XML file: |
Specify the name of the XML input file. The default file extension is ".xml". |
Diagnostic file: |
Specify the file name for diagnostic information generated by this command. If no file name is supplied, all diagnostic information will be displayed in the EDMsupervisor output window. |
Remote schema: |
The name of the Express Schema in the remote EDMdatabase to be used as base for the imported data. |
Options:
accumulating command output: |
A global option that appends the command output to the EDMsupervisor output window. Otherwise the output window is refreshed and only the last command output is displayed. |
match selected input: |
A global option that specifies that only items that partly or exactly matches the string in the related argument input field when activating a Select button, will be in the selection list. An empty (blank) string will match all items. |
header model only: |
Not yet implemented. |
parse only |
The specified XML file will be parsed only, i.e. only checked for syntactical correctness, no data will be stored in the EDMdatabase. |
deleting existing model |
Delete model with given name before operation, if it already exists. |
add to existing model |
The created instances will be added to the specified model, if it already exists. |
user controlled inverse: |
To safeguard consistency inverse attributes are set/updated implicitly by EDM, and users are prohibited from modifying such attributes. When this option is enabled, control of inverse attributes is left to the user/application. |
unpacked model: |
Setting this option enables the model to operate in fragmented form – i.e. de-allocated space is not recovered. This setting may enable improved performance to the cost of more disc space usage. If this option is not set, the de-allocated space of the actual model will be recovered. |
no instance references: |
No "instance references tables" will be created and maintained in the actual model. The built in function USEDIN will not work correctly on such models. |
delete instances with refs: |
Setting this option will permit instances in the actual model to be deleted even though the instances are referenced by other instances, i.e., one or more other instances have one or more relations to the actual instance to be deleted. Instances that are referred to by any other instances cannot be deleted before all the references are deleted except when this option is set. |
delete instance refs on delete: |
The delete instance operation on instances in the actual model will be legal for instances with references. The references to the actual instances will automatically be deleted when the actual instance is deleted. |
log to file: |
Logged information will be stored in a file specified by the <Log file> argument. |
log to stdout |
Logged information will be displayed in EDMsupervisor output window. |