Re: [sqlite] Datetime issue with the time part

Eric Minbiole wrote: > From what you describe, it seems that the compiler is performing > single-precision, rather than double-precision, math. After a quick > Google search, I found a few posts indicating that Direct3D silently > switches the FPU from double to single precision math,

Re: [sqlite] Datetime issue with the time part

> Once again, all of these problems doesn't happen before the creation of > the Direct3D device. Does anyone ever used SQLite successfully in a > full-screen 3D game ? From what you describe, it seems that the compiler is performing single-precision, rather than double-precision, math. After

Re: [sqlite] Datetime issue with the time part

Eric Minbiole wrote: > Sebastien Robillard wrote: > >> Hi everyone, >> I have an issue with datetimes that doesn't return the "time" part >> correctly (always 00:00:00 or 18:00:00) when I use SQLite in my C++ >> code. Whenever I use datetime('now'), or current_timestamp, the time is >>

Re: [sqlite] Datetime issue with the time part

Sebastien Robillard wrote: > Hi everyone, > I have an issue with datetimes that doesn't return the "time" part > correctly (always 00:00:00 or 18:00:00) when I use SQLite in my C++ > code. Whenever I use datetime('now'), or current_timestamp, the time is > not correct. However, it works

[sqlite] Datetime issue with the time part

Hi everyone, I have an issue with datetimes that doesn't return the "time" part correctly (always 00:00:00 or 18:00:00) when I use SQLite in my C++ code. Whenever I use datetime('now'), or current_timestamp, the time is not correct. However, it works correctly when using the sqlite3