-
Notifications
You must be signed in to change notification settings - Fork 7
Sessions aren't correctly stored #3
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
Comments
@yoshuawuyts when you store a session you should be updating an already existing session. So this line here should do a Something to consider for
|
@lrlna sounds like you're talking about an upsert here, perhaps you're looking for replace_one |
@mbroadst i was precisely looking for an upsert but couldn't find |
Each request we make creates a new session id entry in the database. It seems we're probably doing something wrong. The result is that the counter isn't updated and we keep opening new sessions.
Related issues: #1, http-rs/async-session#10, http-rs/tide#664
cc/ @lrlna
Repro
cargo run --example session
Screenshot
The text was updated successfully, but these errors were encountered: