I found an issue that the date stored in the database wasn't being stored as UTC. I've changed all date methods to reference the UTC value. It might be worth mentioning that getTime/setTime are UTC relative methods while all else are timezone relative unless otherwise specified.
Since this might break everyone that has used tedious before it might be beneficial to make this type of conversion to be a configuration setting. What do you think?
Fixing problem with UTC date storage
Would this explain issue #95?
Yeah I think so. I was seeing similar problems on my end.
Btw just noticed the tests failed I'll get on fixing them
Changing EPOCH to be UTC and days to be written as Int32 as per spec …
Changing value parser to account for different js and tds epoch date
Adding UTC marker to datetime test
Glade you had some tests around this. When looking at the test I realized that I didn't account for the difference in tds and js epoch. Everything should be working now.
Also I noticed that when datetime is being written that it was using a UInt for days when it should just use Int. I believe pull request #106 fixed part of this. Looks like small date should both be UInt though.
zero length varchar params don't work unless a length greater than ze…
…ro is specified
Merge pull request #1 from markgardner/varchar-param
zero length varchar params don't work unless a length greater than zero ...
#95 #108 #133 - Option to choose whether to pass times in UTC or loca…