-
Notifications
You must be signed in to change notification settings - Fork 22
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
time features by default #42
Comments
It conflicts with originally sqlx/chrono in my code. |
If you would like to make a PR that enables either choice, I'm happy to review. |
@1g0rkR I dont love how I implemented it but my fork here is working with chrono: https://github.com/vinnymeller/tower-sessions-sqlx-store as stated in the readme I do not recommend at all using it - but you can at a minimum you can see which part(s) of the code need to be updated to support chrono edit: if nobody has gotten to it i will look to make the changes neater & make a pr in a few weeks when I'm back from vacation |
maybe something like this? #46 |
mostly from @vinnymeller |
This is why |
Is there a way to disable time somehow? Because it causes a circular break with sqlx right now |
Yeah, is there a recommended solution? edit: actually, I reminded that I didn't actually care about chrono and migrated my app from chrono to time, no biggie |
I migrated my ${Something}Row structs to the time crate and made two functions that convert back and forth between chrono and time. |
Probably the feature selection can be removed entirely and replaced with something like this: https://github.com/maxcountryman/underway/blob/40f8f899587cb0125e2b8897a4349d2f9c0a391d/src/timestamp.rs which then is used in the crate here as a type override (note that this is particularly ugly in the linked example, but in practice could be cleaned up). Doing so allows e.g. https://github.com/maxcountryman/underway/blob/40f8f899587cb0125e2b8897a4349d2f9c0a391d/Cargo.toml#L15-L19. |
Hi there,
Would be possible to have a choice between time and chrono of sqlx?
I would appreciate for such opportunities.
The text was updated successfully, but these errors were encountered: