-
Notifications
You must be signed in to change notification settings - Fork 27
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
TIMESTAMP WITH ZONE #19
Comments
Hi, is this repo still active, I would like to do some other dependencies update/making changes, etc.. |
Yes, this repo is still active. I somehow was not watching it, so I did not see notifications. I don't know how that happened, but it's resolved now. As far as TIMESTAMP WITH ZONE, I don't exactly recall why I chose that. If your sessions table is large enough that the storage size is relevant, I imagine there's additional db tuning we'd want to look at. |
Thanks for replying @jbr Yeah not critical, just that I try to avoid |
This makes sense. I'd be amenable to making this change, but we'd need to think through how to do migrations and track table versions, which was something I put off "for later" |
Ah I was thinking just keep |
Very minor thing but I wonder why we would want to store TIMESTAMP WITH ZONE, it is probably better not to store ZONE and the code is using
Utc::now
anyway.https://github.com/jbr/async-sqlx-session/blob/main/src/pg.rs#L157
The text was updated successfully, but these errors were encountered: