|
The extended options supported for database creation utilities like ulcreate, ulinit, and ulload are the same creation-time properties you can set when configuring any new database. You can define extended database creation-time options in one of two ways:
Prepend each extended option with -o For example, if you want to create a database with ulcreate so that the database is created with case sensitivity enabled and uses ISO-compatible date formatting and ordering, run the command as follows:
ulcreate -o case=respect -o date_format=YYYY-MM-DD -o date_order=YMD
Assemble options into a creation-string An assembly of creation parameters is called a creation-string. You type a creation-string on a single line with the parameter names and values separated by semicolons:
parameter1=value1;parameter2=value2The UltraLite runtime ensures the creation-time parameters are assembled into a creation-string before creating a database with it. For example, if you use the ulcreate utility, the following connection string is used to create a new database with case sensitivity enabled and that uses ISO-compatible date formatting and ordering:
ulcreate - o "case=respect;date_format=YYYY-MM-DD; date_order=YMD"
You must always configure database creation properties at creation time. You cannot alter these properties once the file has been written.
| Property list | Description |
|---|---|
|
case |
Sets the case-sensitivity of string comparisons in the UltraLite database. See UltraLite case sensitivity considerations and UltraLite case property. |
|
checksum_level |
Sets the level of checksum validation in the database. See Verifying page integrity with checksums and UltraLite checksum_level property. |
|
collation |
Sets the collation sequence used by the UltraLite database. Setting this property with/without the UTF-8 property determine the character set of the database. See UltraLite character considerations and UltraLite collation property and UltraLite utf8_encoding property. |
|
date_format |
Sets the default string format in which dates are retrieved from the database. See UltraLite date considerations and UltraLite date_format property. |
|
date_order |
Controls the interpretation of date ordering of months, days, and years. See UltraLite date considerations and UltraLite date_order property. |
|
fips |
Controls AES FIPS compliant data encryption, by using a Certicom certified cryptographic algorithm. FIPs encoding is a form of strong encryption. See UltraLite security considerations and UltraLite fips property. |
|
max_hash_size |
Sets the default index hash size in bytes. See UltraLite index performance considerations and UltraLite max_hash_size property. |
|
nearest_century |
Controls the interpretation of two-digit years in string-to-date conversions. See UltraLite nearest century conversion considerations and UltraLite nearest_century property. |
|
obfuscate |
Controls whether or not to obfuscate data in the database. Obfuscation is a form of simple encryption. See UltraLite security considerations and UltraLite obfuscate property. |
|
page_size |
Defines the database page size. See UltraLite page size considerations and UltraLite page_size property. |
|
precision |
Specifies the maximum number of digits in decimal point arithmetic results. See UltraLite decimal point position considerations and UltraLite precision property. |
|
scale |
Specifies the minimum number of digits after the decimal point when an arithmetic result is truncated to the maximum precision. See UltraLite decimal point position considerations and UltraLite scale property. |
|
time_format |
Sets the format for times retrieved from the database. See UltraLite time considerations and UltraLite time_format property. |
|
timestamp_format |
Sets the format for timestamps retrieved from the database. See UltraLite timestamp considerations and UltraLite timestamp_format property. |
|
timestamp_increment |
Determines how the timestamp is truncated in UltraLite. See UltraLite timestamp considerations and UltraLite timestamp_increment property. |
|
utf8_encoding |
Encodes data using the UTF-8 format, 8-bit multibyte encoding for Unicode. See UltraLite character considerations and UltraLite utf8_encoding property. |