The following table lists all possible USYS$UD7_PARAMS assignments.
UD7 driver options
OptionPossibleDescription
values †
SUPPRESSZEROENABLE*,
DISABLENumerics have/don’t have leading zeroes
NOKEYCHECK ENABLE,
DISABLE*Do not check for duplicate primary keys on write. This option should be used when writing ‘dumps’ of a table, it improves the performance considerably.
Note: The UD7 driver only ever checks the PRIMARY key (key number 1) for uniqueness, not other ‘candidate’ keys.
GOOKfilenameRandomly encrypt the fields named in filename. This is useful for producing test data. Note: the fields are not qualified, so if you have two fields with the same name, or part-name, then both will match. Eg:
Table1 has 2 fields rat and rathelsdorp. If I put the field name rat in the file called filename then both the field rat and rathelsdorp are converted.
The file must have 1 one only 1 line.
PRA ENABLE*,
DISABLEIf you wish to use the delete function then PRA must be disabled.
LEFTTRIMDISABLEStrings Don’t/have leading spaces
RIGHTTRIMDISABLEStrings don’t/have trailing spaces
TRANSLATECHARSBINARY, or
a sequence of
escape codes to
translate.
\aalert (bell) character\\backslash
\bbackspace\?question mark
\fformfeed\’single quote
\nnewline\"double quote
\rcarriage return
\thorizontal tab
\vvertical tab
The default characters to translate are \n and \r. To use this option you must also set translate.
If BINARY is specified all non-ASCII characters are translated into \xhh and \ is translated to \\. If BINARY is not specified, then all Uniface BINARY types (Raw, and VC* for instance) are mapped to the TRX data type. Note: if the entity (not the field) has an interface definition that maps it to TRX then the BINARY parameter will not effect it (eg: FORMPIC.UFORM.DICT). Using TRANSLATECHARS BINARY uses more space in your XML-DATA file and is slower to process. Use TRANSLATECHARS BINARY only if you need to process binary data outside of Uniface.
OPTLOCKINGDISABLE*If set use optimistic locking as default.
TRANSLATEDISABLETranslate cr & lf into \r & \n and translate \ to \\.
Do not disable this feature without first carefully checking your data for Special Strings (SS) that contain carriage returns.
If a line ends in the XML-DATA file with a carriage return then an entire record may not have been entirely read if one of the fields has an embedded carriage return.
If you are reading the XML-DATA file outside of the UD7 driver, you also need to take into account cases where the last field is NULL.
BUFFERsizeBuffer Input operations with a buffer size bytes. This value is set to 8100 bytes by default, and for optimal speed, should be set to the average record length.
PREFIX ENTITY NAMES
DISABLE*Since XML tags must be unique, and Uniface Field and Entity names do not, you can end up with invalid XML if you have field and entity names that are the same. To correct this problem use PREFIX ENTITY NAMES.
This option forces all entity name tags to be prefixed with XML (uppercase).
Note * = default.
† =If the "Possible values" column is blank, this indicates that the option is disabled by default and enabled if the option is listed, eg: USYS$SOL_PARAMS listoptions enables this feature.
$Revision: 1.10 $ $Date: 2011/02/28 02:56:33 $ | [go to top] |