The equivalent is cf_sql_timestamp. The cfsqltypes are just a wrapper around the types used by jdbc ie java.sql.Types. (So you can probably blame java for the inconsistent naming convention.)
Types:
cf_sql_date => java.sql.Types.DATE => java.sql.Date
cf_sql_timestamp => java.sql.Types.TIMESTAMP => java.sql.TimeStamp
Description:
- DATE consists of day, month, and year.
- TIMESTAMP combines DATE and TIME and also adds in a nanosecond field.
http://download.oracle.com/javase/1.3/docs/guide/jdbc/spec/jdbc-spec.frame8.html
So the behavior you are seeing is expected.
>> So how to deal with datetime columns?
It depends on your database and what you are storing: date or date and time. Since I use MS SQL 2005, I prefer to cf_sql_timestamp all the time, and truncate the time with CF functions when needed.
-Leigh
| >> It's supposed to answer the question. |
| Well, I do not know if it _did_ or not .. ;-) But hopefully it conveyed: a) that is the correct behavior and b) the same behavior exists on ACF -Leigh |