My guess is that it's a lot more portable to use a long value of the java.util.Date.getTime(). Timestamp relies on the DB having the same exact clock as the app, and don't even get me started talking about TimeZones....
I'm +1 on just storing that long value. Paul -----Original Message----- From: James Stauffer To: '[EMAIL PROTECTED]' Sent: 5/15/04 3:55 AM Subject: DBAppender: logging_event.timestamp: Number instead of timestamp In DBAppender why is logging_event.timestamp a number instead of timestamp? James Stauffer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
