[Building Sakai] Timezone for events

[David Horwitz]

In fact looking at the code (way down in BaseSqlServlce) this is down to 
how the sql service handles Time objects passed in fields to prepared 
statements.

They all get cast to a java.sql.TImeStamp constructed with a GMT 
timestamp. I think the different oracle/mysql behaviour has more to do 
with how the drivers handle datetime objects and should be visible 
across a number of classes.  Using a database type that stores the 
timezone should be safer, particularly on DST changes, but should have 
little effect on the actual date stored - unless there is something very 
wrong anyway.

I've tested the mysql change from DateTime to Timestamp and the 
behaviour is the same.

D

On 05/23/2011 03:55 PM, Stephen Marquard wrote:
> Oracle users may know their events table to be in GMT, but mysql users
> know it to be in localtime. Our SAKAI_EVENT records are in GMT+2 which
> is our local timezone.
>
> So it looks like changing it will inevitably break any external
> assumptions for at least one set of institutions.
>
> Regards
> Stephen
>
>