Eureka - I think I found the problem. The column in question was created with a DEFAULT current_timestamp attribute (pulling the sytem time when a record was inserted into the table), for which the default precision has changed for recent releases of PostgreSQL.
From the PG 7.3.1 manual (http://www.us.postgresql.org/users-lounge/docs/7.3/postgres/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT) "CURRENT_TIME, CURRENT_TIMESTAMP, LOCALTIME, and LOCALTIMESTAMP can optionally be given a precision parameter, which causes the result to be rounded to that many fractional digits. Without a precision parameter, the result is given to the full available precision. Note: Prior to PostgreSQL 7.2, the precision parameters were unimplemented, and the result was always given in integer seconds." These two sections tell me why I've never noticed this before. A) Apparently the systime on Linux has greater precision than on Windows B) I upgraded my Linux server right from 7.1.2 to 7.3.1, missing 7.2 entirely Apparently CF5's DateFormat() function can't cope with the extreme precision of the Linux system clock.. -B _____ Brian Panulla [EMAIL PROTECTED] Chief Information Officer 814.867.4087 Elmwood Media Group www.elmwoodmedia.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=14 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=14 Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14
