Skip to content
New issue

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

Support chrono for SQLite #164

Closed
mehcode opened this issue Mar 26, 2020 · 3 comments
Closed

Support chrono for SQLite #164

mehcode opened this issue Mar 26, 2020 · 3 comments
Labels
db:sqlite Related to SQLite E-medium enhancement New feature or request

Comments

@mehcode
Copy link
Member

mehcode commented Mar 26, 2020

No description provided.

@mehcode mehcode added enhancement New feature or request db:sqlite Related to SQLite E-easy E-medium and removed E-easy labels Mar 26, 2020
@felipesere
Copy link
Contributor

My current app that I am experimenting with uses a few TIMESTAMP columns which I have mapped to chrono::NaiveDateTime.

I could try to implement Encode<Sqlite> and Decode<Sqlite> based how Diesel does it?

https://docs.diesel.rs/src/diesel/sqlite/types/date_and_time/chrono.rs.html#56-97

@mehcode
Copy link
Member Author

mehcode commented Mar 31, 2020

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 ).

I'd expect DATETIME and TIMESTAMP to be equivalent.

Diesel seems to have the right idea but from a skim it seems that they don't support UNIX seconds.

@felipesere
Copy link
Contributor

Taking this one 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
db:sqlite Related to SQLite E-medium enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants