Be aware of a Windows OS bug that prevents correct conversion of epoch integers to local date/time due to the recent US DST change:
http://www.sqlite.org/cvstrac/tktview?tn=2322 Assuming you've applied the Windows OS DST patch, epoch-converted times can be off by an hour for pre-2007 dates in the time periods that used to not be be in daylight savings time, but are now as of 2007. SQLite relies on the underlying OS to handle these timezone/DST issues. In Windows versions prior to Vista, Windows only keeps one DST record per timezone - regardless of different past DST periods. --- Mitchell Vincent <[EMAIL PROTECTED]> wrote: > The issue isn't with SQLite at all, actually, but with the ODBC > driver. I guess the ODBC driver "trusts" SQLite's data type > description because I have a field called "timestamp" that actually > stores an epoch integer in it and ODBC-aware applications see the > datatype as "DateTime" and refuse to pass through the data. So I > really just need to change the type description inside SQLite so it > will report integer to the ODBC driver. And since there are a *lot* of > databases with this problem I'd love to be able to just issue some > sort of update through SQLite to make that happen. ____________________________________________________________________________________ Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
