Re: [pmacct-discussion] MySQL Timezone handling

2016-05-31 Thread Jentsch, Mario
> I just feel that running the server clock in UTC will be a bit > uncomfortable having to constantly translate the dates from UTC to > UTC+2/3 while working with logs etc. Sounds like you don't have server in different time zones... believe me, merging log data stored with local time from

Re: [pmacct-discussion] MySQL Timezone handling

2016-05-31 Thread Vaggelis Koutroumpas
Thanks for your suggestion guys, How do you propose to work with UTC? Should the OS' clock run in UTC or only the MySQL server? I just feel that running the server clock in UTC will be a bit uncomfortable having to constantly translate the dates from UTC to UTC+2/3 while working with logs etc.

Re: [pmacct-discussion] MySQL Timezone handling

2016-05-31 Thread raf
+1 to storing your application data in UTC. +1. Your server and storage backend should be set to UTC. This is the only way to assure consistency of timestamped data. Zoning should be make on the frontend side. -- Raphael Mazelier ___