Could this change be protected via rc? UNB1 is at present really flexible and consistent concerning the use of time zones: any stored data is in the server's time zone, any displayed data is either in the board's time zone (for guests) or in the user's time zone. In fact, I really think it is the right thing(TM) that stored and displayed time zone are treated separately.Quote by Yves:What happened by now: I have changed the code as suggested by Saxtus. So all timestamps are converted to the board's default timezone, respecting the board's default DST switch, before a log line is written[...]
So, in order to being able to interpret the times of my old log files (of course, under the condition that board and server time do not coincide) I have to switch the board time (and I have to write down the time of the update in order to identify the time zone inside my logfiles)?!?The only effects this has on the uniqueness of log entries:
- When updating the board code from yesterday to tomorrow, log entries' timestamps may either skip to the future or repeat a few hours. If the board timezone and system timezone already match, nothing changes at all.
Please, at least briefly try my suggestion. This way nothing has to be changed on-disk, and there can even be administrators in different time zones, which get adapted times. Take as primary reason: that's just how it works anywhere else in the board...Converting to UTC instead of board timezone only eliminates the second point, but introduces massive deviations from day breaks comparing to any local timezone. [...]
Pretty, pretty please: no or not without an option to disable this change...As I said, the change of the log timezone to the board's default timezone will be included in the next release. I hope to get some more pending changes done tomorrow and put up a new code snapshot at last until the weekend.
Listen, Yves...Quote by Saxtus:but correct time is of the essence!
Quote by jense:Take as primary reason: that's just how it works anywhere else in the board...
Hm, are you sure? I exactly checked that and found something like EditDate = time(), i.e. *local* time. I'll recheck.Quote by Yves:It's not. Anywhere else a UNIX (UTC) timestamp is stored in the database.
...rebooting... yes, of course. After reading everything about, date(), time(), gmdate(), gmmktime() I got apparently pretty much confused.Quote by Yves:time() returns a UNIX timestamp (seconds since 1970-01-01T00:00:00+00:00), and those are always in UTC.
Sidenote: with the DateTime class (as of PHP 5.2?!), playing with time zones is possible without even touching the local server time. Almost everything can be done then (call it overkill)...Quote by Yves:This is not specified yet.
Page: 
Saxtus
Show profile
Link to this post
This post was edited on 2009-03-05, 19:56 by