This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I'm having some issues getting the UpdatedOn fields to use UTC. I have set my context's AutoTimestampMode property to AutoTimestampMode.Utc and I have confirmed using a watch that this value is set correctly. But still my UpdatedOn fields are being written with the local time. Is there a bug with this or am I misunderstanding how this should work? What I am assuming is that Lightspeed is meant to take the local time and then, using the timezone setting, convert this local time to UTC and write it to the database. Is this a correct assumption or have I got completely the wrong idea about this feature? BTW I am using the free version of Lightspeed and it's the 30 July 2009 nightly build. Thanks Andrew Dixon |
|
|
|
|
You're not misunderstanding. LightSpeed grabs the UTC time from the local machine and writes that to the database, and this is working in our test environment. Could you capture the generated SQL (context.Logger = new TraceLogger() and context.VerboseLogging = true) and post it for us to have a look at please? Thanks! |
|
|
|
|
Hi Ivan, Thanks for the fast response. But it turns out I'm just an idiot. As soon as I looked at the logger output I realised that UTC is currently 12 hours behind NZ time and that Lightspeed is converting to UTC. I just wasn't observant enough to notice that the times Lightspeed was writing to the DB were 3:xx am and not pm. Very sorry to have wasted your time. But glad that all is working as it should. Thanks Andrew
|
|
|
|
