- see footer for list info -<
Hey thanks for your reply ;) I'll look into that!
The solution was actually quite easy as we have a duration... so to get the end, I simply added that on. I did still need to find out what the problem is so that I don't have this issue again. On 27/03/07, Jatin Nanda <[EMAIL PROTECTED]> wrote:
>- see footer for list info -< Recently the JVMs handling of daylight savings has been changed. I would check your version of JVM. Unfortunately, I'm not sure what the solution is - but try Peter J Farrel's (coldfusion podcast guy) blog. Hope this helps On 3/27/07, Tom Shearer (lists) <[EMAIL PROTECTED]> wrote: > > >- see footer for list info -< > Hi All, > > After some digging I found that JDBC converts the dates to a string using > a > timezone offset set on the server... bloody windows. why it would only do > it at that time is completely beyond me. > > I decided to cast the dateTime field as a varchar, and voila - it gave me > exactly what I need. > > I feel it's a large bag of poo, and we should all use UTC and change our > dates accordingly based on the timezone offset :) Atleast it would be > right > all the time then :) > > Tom > > On 27/03/07, Tom Shearer (lists) <[EMAIL PROTECTED]> wrote: > > > > hi All, > > > > I have some data in a sql server 2000 database that looks like: > > > > startDate (dateTimefield) endDateI (dateTimeField) > > '2007-03-25 01:52:32.000' '2007-03-25 02:05:32.000' > > '2007-03-25 00:52: 32.000' '2007-03-25 01:05:32.000' > > > > When I query the database in cf the resultset returned looks like this: > > > > startDate (dateTimefield) endDateI (dateTimeField) > > '2007-03-25 02:52:32.000' '2007-03-25 02:05:32.000' > > '2007-03-25 00:52:32.000' '2007-03-25 02:05:32.000' > > > > As you can see the first line startDate is an hour ahead of what's in > the > > db. Also notice the second record - it now has an edDate that is an > hour > > ahead of what's being stored. > > > > I've been through the knowledge base and check it updated the jvm incase > > it's some screwy timezone thing, but that didn't make a difference... > > > > We do know that if the record started and end before 2am it's ok and an > > hour ahead - this is fine. If the record started and ended after 2am > it's > > also fine. > > > > Any idea why this maybe happening, and could it be something to do with > > the JDBC connection settings? > > > > I know this problem occurs for UK BST time, but I wouldn't expect > > Coldfusion to assume it knows how I want to handle this, as the data is > > correct in sql server. > > > > Thanks, > > > > Tom > > > _______________________________________________ > > For details on ALL mailing lists and for joining or leaving lists, go to > http://list.cfdeveloper.co.uk/mailman/listinfo > > -- > CFDeveloper Sponsors:- > >- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -< > >- Lists hosted by www.Gradwell.com -< > >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help > -< > _______________________________________________ For details on ALL mailing lists and for joining or leaving lists, go to http://list.cfdeveloper.co.uk/mailman/listinfo -- CFDeveloper Sponsors:- >- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -< >- Lists hosted by www.Gradwell.com -< >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
_______________________________________________ For details on ALL mailing lists and for joining or leaving lists, go to http://list.cfdeveloper.co.uk/mailman/listinfo -- CFDeveloper Sponsors:-
- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -< - Lists hosted by www.Gradwell.com -< - CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
