TZ is not used and is not set in our environment. Using "GetLocalTime()" instead of "localtime()" should solve the problem.
-----Urspr?ngliche Nachricht----- Von: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-bounces at mailinglists.sqlite.org] Im Auftrag von Igor Tandetnik Gesendet: Donnerstag, 23. Juli 2015 14:41 An: sqlite-users at mailinglists.sqlite.org Betreff: Re: [sqlite] changed time zone On 7/23/2015 4:11 AM, Bruno Schw?gli (CTModule AG) wrote: > We use SQLite in an environment (ships) where a time zone change can happen > during normal operation. We then set the time zone of the system (windows) > accordingly. > Running SQLite instances do not respect this change. So Time('now') and > Time('now', 'localtime') still return the same values but in my opinion > Time('now', 'localtime') should respect the new time zone. Have the host application listen to WM_SETTINGCHANGE message. When you detect time zone change, delete TZ environment variable (with _putenv or SetEnvironmentVariable ) and call _tzset -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
