We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
My current app that I am experimenting with uses a few TIMESTAMP columns which I have mapped to chrono::NaiveDateTime.
TIMESTAMP
chrono::NaiveDateTime
I could try to implement Encode<Sqlite> and Decode<Sqlite> based how Diesel does it?
Encode<Sqlite>
Decode<Sqlite
https://docs.diesel.rs/src/diesel/sqlite/types/date_and_time/chrono.rs.html#56-97
Sorry, something went wrong.
From reading sqlite documentation, all times should be UTC.
So it'd be correct to map to both DateTime<UTC> and NaiveDateTime ( with the former preferred ).
DateTime<UTC>
NaiveDateTime
I'd expect DATETIME and TIMESTAMP to be equivalent.
DATETIME
Diesel seems to have the right idea but from a skim it seems that they don't support UNIX seconds.
Taking this one 😄
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: