If it is me, I would store the date in two columns. One in Timezone of user, and the other in UTC timezone. Another way is just store in UTC and just convert on the fly when you need to display a page, depending on timezone of user. On Mon, Feb 23, 2015 at 2:15 PM, Piers <piers@xxxxxxxxxxx> wrote: > Hi there, > > I have an app with users in one timezone with the date / time stored in > their location. Now there are more users in more locations and I would like > to support them - ideally without changing to historical data. > > At the moment the app uses a time offset field to allow two people to see > one note expressed in their timezone. > > There are two use cases for this one is the free/busy calendar, the other > is the meeting invite ICS file. > > At the moment I would like to support ICS which are GMT based. > > My guess is that: > > * Assign each user to their own timezone > * I take the diary row ($start_date, $start_time) and convert it to a GMT > timestamp > * Make the ICS file > > I am keen to hear of better solutions or ideas. > > Cheers > > P > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- I love Java <http://javadevnotes.com/java-integer-to-string-examples>
