Re: [sqlite] Changing Schema On The Fly

Thanks Joe! I store "date" values as noon on the given day and toss out the time part to keep things like this from effecting my software. I appreciate the information though! On 5/31/07, Joe Wilson <[EMAIL PROTECTED]> wrote: Be aware of a Windows OS bug that prevents correct conversion of

Re: [sqlite] Changing Schema On The Fly

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

Re: [sqlite] Changing Schema On The Fly

Yes, I've read that. 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

Re: [sqlite] Changing Schema On The Fly

If you read you will see that, "Each value stored in an SQLite database (or manipulated by the database engine) has one of the following storage classes: NULL. The value is a NULL value. INTEGER. The value is a signed integer, stored in 1, 2, 3, 4, 6, or 8

[sqlite] Changing Schema On The Fly

I have a set of databases that contain a date type called "timestamp". I need to make those "integer" so they come through the ODBC driver the right way. Is there any way to change all of that through queries on-the-fly? I'd like to avoid re-creating all the databases if possible.. Thanks! -- -