Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DateTimeOffset Conversion
See original GitHub issueAccording to the docs, DateTimeOffset is converted to UTC before sending it. So for example,
new DateTimeOffset(2012, 1, 1, 1, 1, 1, TimeSpan.FromHours(-6))
1/1/2012 1:01:01 AM -06:00
Gets converted to:
1/1/2012 7:01:01 AM +00:00
When inserted into the database.
This is great. However, when pulling this value out of the database, the following is returned:
1/1/2012 7:01:01 AM -06:00
It appears that npgsql is using the local timezone when values are pulled out, even though npgsql inserted a UTC offset’ed value.
I would expect either:
1/1/2012 *1*:01:01 AM -06:00
or
1/1/2012 *7*:01:01 AM +00:00
Either is fine since the time is equivalent, but this is definitely not correct:
1/1/2012 *7*:01:01 AM *-06:00*
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@roji I pulled down the driver to figure out what the issue was, and there wasn’t any issues.
A little embarrassing - I tested everything again in linqpad and everything looks good. My only excuse is sleep deprivation. Sorry to waste everyone’s time.
@Silvenga @austindrenski am re-opening so I can take another look, to make sure that we’re doing the right thing. Will try to look at this soon.