Re: [sqlite] datetime('now', 'utc') vs. CURRENT_TIMESTAMP

2009-08-26 Thread Wilson, Ronald
> According to http://www.sqlite.org/lang_datefunc.html datetime('now') > returns date and time already as UTC. If you add 'utc' modifier then > it makes datetime() think that it's your local time and convert it to > 'utc' thus adding 4 hours (apparently you're in GMT -4 timezone). Thanks. I

Re: [sqlite] datetime('now', 'utc') vs. CURRENT_TIMESTAMP

2009-08-25 Thread Jay A. Kreibich
On Mon, Aug 24, 2009 at 06:21:49PM -0400, Wilson, Ronald scratched on the wall: > According to the documentation for CURRENT_TIMESTAMP, it should insert > the current UTC date/time: http://www.sqlite.org/lang_createtable.html. > sqlite> select datetime('now', 'utc'); > > 2009-08-25 02:20:10 >

Re: [sqlite] datetime('now', 'utc') vs. CURRENT_TIMESTAMP

2009-08-25 Thread Pavel Ivanov
> Do I misunderstand something fundamental? According to http://www.sqlite.org/lang_datefunc.html datetime('now') returns date and time already as UTC. If you add 'utc' modifier then it makes datetime() think that it's your local time and convert it to 'utc' thus adding 4 hours (apparently you're

[sqlite] datetime('now', 'utc') vs. CURRENT_TIMESTAMP

2009-08-25 Thread Wilson, Ronald
According to the documentation for CURRENT_TIMESTAMP, it should insert the current UTC date/time: http://www.sqlite.org/lang_createtable.html. However, there appears to be a mismatch with datetime('now', 'utc'): SQLite version 3.6.10 Enter ".help" for instructions Enter SQL statements