You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently (0.8.1) when reading/writing Time values the format SQLite3::DATE_FORMAT is used. This is one of the supported formats by sqlite. It is actually the one with more precision: YYYY-MM-DD HH:MM:SS.SSS
This is enough for reading/writing values using Time crystal's type. But it would be proper to allow reading time values using a fallback for all other DateTime formats described in https://www.sqlite.org/lang_datefunc.html so the following queries will work:
Currently (0.8.1) when reading/writing Time values the format
SQLite3::DATE_FORMAT
is used. This is one of the supported formats by sqlite. It is actually the one with more precision:YYYY-MM-DD HH:MM:SS.SSS
This is enough for reading/writing values using
Time
crystal's type. But it would be proper to allow reading time values using a fallback for all other DateTime formats described in https://www.sqlite.org/lang_datefunc.html so the following queries will work:select date('now');
select datetime('now');
SELECT current_timestamp;
This should be handled in
crystal-sqlite3/src/sqlite3/result_set.cr
Line 59 in 9784573
The text was updated successfully, but these errors were encountered: