Integer, between 1 and 1000000 inclusive

1

Can be set for an individual connection or for the PUBLIC group. Takes effect immediately.

Since a TIMESTAMP value is precise to six decimal places in SQL Anywhere, by default 1 microsecond (0.000001 of a second) is added to differentiate between two identical TIMESTAMP or TIMESTAMP WITH TIME ZONE values.

When several rows containing a column with the DEFAULT TIMESTAMP or DEFAULT UTC TIMESTAMP attribute are updated and the column itself is not explicitly updated, the column receives a unique value for each row being updated. For example, three rows containing a column of type TIMESTAMP WITH TIME ZONE with the DEFAULT UTC TIMESTAMP attribute are updated. The rows are updated at '2011-04-01 12:47:52.724000+00:00', however each row contains a unique UTC TIMESTAMP value.

2011-04-01 12:47:52.724000+00:00
2011-04-01 12:47:52.724001+00:00
2011-04-01 12:47:52.724002+00:00

Some software, such as Microsoft Access, truncates TIMESTAMP values to three decimal places, making valid comparisons a problem. You can set the truncate_timestamp_values option to On to specify the number of decimal place values SQL Anywhere stores to maintain compatibility.

For MobiLink synchronization, if you are going to set this option, it must be set before performing the first synchronization.

• truncate_timestamp_values option
• TIMESTAMP special value
• UTC TIMESTAMP special value
• default_timestamp_increment connection property