Skip to content

Support for DateTimeOffset#239

Merged
praeclarum merged 1 commit into
praeclarum:masterfrom
revaultch:master
Feb 11, 2014
Merged

Support for DateTimeOffset#239
praeclarum merged 1 commit into
praeclarum:masterfrom
revaultch:master

Conversation

@revaultch

Copy link
Copy Markdown

As mentioned in #217
Saving a DateTime is probably not what people want in most cases.

DateTime represents the same date and time agnostic to the timezone, such as if you wanted to describe "the start time of thanks giving dinner" across multiple timezone, or opening hours of shops.

From the article at http://msdn.microsoft.com/en-us/library/bb384267.aspx:
"...
Note
These uses for DateTimeOffset values are much more common than those for DateTime values. As a result, DateTimeOffset should be considered the default date and time type for application development.
..."

@praeclarum

Copy link
Copy Markdown
Owner

Love this as it makes the DateTime storage debacle go away. :-)

praeclarum added a commit that referenced this pull request Feb 11, 2014
@praeclarum
praeclarum merged commit fb1156e into praeclarum:master Feb 11, 2014
@mawarnes

Copy link
Copy Markdown

would it be fair to say that any datetimes stored are TZ agnostic, therefore if your policy is to make sure all datetimes that are stored are UTC, then set the DateTimeKind upon retrieval from the sqlite db?

github-actions Bot pushed a commit to Reddevildragg-UPM-Forks/sqlite-net that referenced this pull request Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants