Specifies whether InfoMaker should map DateTime and Time datatypes to the Oracle TimeStamp datatype.
O90 Oracle9i
O10 Oracle 10g
TimeStamp=value
TimeStamp=1
Oracle9i and later databases and the O90 and O10 interfaces support the Oracle timestamp datatype. This datatype includes the date and the time including milliseconds. The existing Oracle Date datatype does not include millisecond information. In a report, both the Oracle Timestamp and Date datatypes are mapped to the InfoMaker DateTime datatype, which supports millisecond information.
If you use the O90 or O10 interface with an Oracle9i or higher server, DateTime and Time datatypes are mapped to the Oracle TimeStamp datatype by default. If you want DateTime and Time to be mapped to the Oracle Date datatype, set the TimeStamp database parameter to 0.
The TimeStamp database parameter does not apply to the O84 database interface. When you use the O84 interface, the DateTime and Time datatypes are always mapped to the Oracle Date datatype.
In InfoMaker 8 and earlier, millisecond information was truncated when used with the Oracle Date datatype. In InfoMaker 9.0 and later, millisecond information is not truncated. As a result, when performing multiple updates to a DateTime field that maps to a Date column, the first update succeeds, but subsequent updates fail with a “row changed between retrieve and update error.”
If you are using the O90or O10 interface with a database that uses only the TimeStamp datatype, InfoMaker handles updates correctly. If you are using the O90 or O10 interface with a database that uses only the Oracle Date datatype, set the DBParm TimeStamp to 0 to truncate millisecond information.
To set the TimeStamp value to treat DateTime and Time DataWindow datatypes as Oracle Date datatypes, clear the Map DateTime/Time to Oracle Timestamp check box on the Syntax page in the Database Profile Setup dialog box.
