DateTimeFormatInfo.CurrentInfo
CultureInfo
https://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo(v=vs.110).aspx
This implementation of SQLite for ADO.NET can process date/time fields in databases in one of six formats.
Remarks
ISO8601 format is more compatible, readable, fully-processable, but less accurate as it does not provide time down to fractions of a second.
JulianDay is the numeric format the SQLite uses internally and is arguably the most compatible with 3rd party tools.It is not readable as text without post-processing.
Ticks less compatible with 3rd party tools that query the database, and renders the DateTime field unreadable as text without post-processing.
UnixEpoch is more compatible with Unix systems.
InvariantCulture allows the configured format for the invariant culture format to be used and is human readable.
CurrentCulture allows the configured format for the current culture to be used and is also human readable.
The preferred order of choosing a DateTime format is JulianDay, ISO8601, and then Ticks. Ticks is mainly present for legacy code support.
Members
Member Name Description
Ticks Use the value of DateTime.Ticks. This value is not recommended and is not well supported with LINQ.
ISO8601 Use the ISO-8601 format. Uses the "yyyy-MM-dd HH:mm:ss.FFFFFFFK" format for UTC DateTime values and "yyyy-MM-dd HH:mm:ss.FFFFFFF" format for local DateTime values).
JulianDay The interval of time in days and fractions of a day since January 1, 4713 BC.
UnixEpoch The whole number of seconds since the Unix epoch (January 1, 1970).
InvariantCulture Any culture-independent string value that the .NET Framework can interpret as a valid DateTime.
CurrentCulture Any string value that the .NET Framework can interpret as a valid DateTime using the current culture.
Default The default format for this provider.