All the more I'm running into scenarios where DateTimeOffset is being used to store dates in SQL Server (in favour of UTC).
What are your thoughts on adding this overload to the SafeDataReader?
I believe this overload is currently specific to the SqlClient data reader, so perhaps we can have the GetDateTimeOffset() overload throw a NotSupportedException if the SafeDataReader was constructed with another type of data reader?
Maybe it's just me, but I would certainly find it useful!
Already registered in the bugtracker:
Copyright (c) Marimer LLC