Upload remote model
This command copy a model from a local single user database to an EDM database managed by an EDM server. If the target database does not contain the schema of the source model, it is possible selecting the appropriate option to have the schema uploaded before the data is uploaded.
Arguments:
Server context name: |
Specify name of server context. |
Remote repository: |
Specify the name of the remote repository to hold the model to be uploaded. Repository names are case sensitive. |
Remote model: |
Specify the name of the target model. Model names are case sensitive. |
Repository: |
Specify the name of the repository holding the model to be uploaded. Repository names are case sensitive. |
Model: |
Specify the name of the model to be uploaded. Model names are case sensitive. |
Remote schema: |
Specify the name of the underlying schema for the target model. Express schema names are case insensitive. |
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. |
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. |
uploading schema if required: |
If the Express schema of the model to upload does not exist in the target database, it is uploaded before the model is uploaded. |
uploading schema: |
The Express schema of the model to upload is uploaded and stored in the target database before the model is uploaded. If there exists a schema with the same name in the target database, an error message is given. |
deleting existing schema: |
If there exist an Express schema in the target database with the same name as the schema of the source model, it is deleted before the model is uploaded. When this option is selected, either the option [uploading schema if required] or [uploading schema] must be selected. |
deleting existing model: |
Delete the target model before operation, if it already exists. |
add to existing model: |
The data in the source model is added to the target model. |
user controlled inverse: |
To safeguard consistency inverse attributes are maintained 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 for this specific model. After the user (user application) has taken control of updating inverse attributes of a data model, this control can never be taken over by EDM again for this particular model. |
unpacked model: |
Setting this option enables the database 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 database 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 for such models. This state can never change in the lifetime of the actual model. |
delete instances with references: |
Setting this option will permit instances 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. So-called dangling pointers in the actual model can be the result of deleting an instance that is referenced by another instance. |
delete instance refs on delete: |
The delete instance operation will be legal for instances with references. The references to the actual instances will automatically be deleted when the actual instance is deleted. |
log errors and warnings only: |
Limits the log to only include logging of instances related to errors and warnings. |
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. |