> 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 in GMT -4 timezone).
Pavel On Mon, Aug 24, 2009 at 6:21 PM, Wilson, Ronald<rwils...@harris.com> wrote: > 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 terminated with a ";" > > sqlite> create table test(stamp DATETIME default CURRENT_TIMESTAMP); > > sqlite> insert into test (rowid) values(1); > > sqlite> insert into test values (CURRENT_TIMESTAMP); > > sqlite> select * from test; > > 2009-08-24 22:19:43 > > 2009-08-24 22:19:55 > > sqlite> select datetime('now', 'utc'); > > 2009-08-25 02:20:10 > > sqlite> > > > > If you ignore the minor time diff from my slow typing, there is a clear > 4 hour difference between CURRENT_TIMESTAMP and datetime('now', 'utc'). > Do I misunderstand something fundamental? > > > > RW > > > > Ron Wilson, Engineering Project Lead > > (o) 434.455.6453, (m) 434.851.1612, www.harris.com > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
