Set last_login_at only on login instead of every single action #1017
Reference in New Issue
Block a user
Delete Branch "change-last_login_at-behaviour"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, every request write to the
userstable updatinglast_login_at. Not sure this adds any value. This PRlimits writing
users.last_login_attoPOST /sessionandPOST /registrationrequests only.I agree with this approach.
For some additional context around this—the original logic was put in a while back when we were attempting to "auto-sync" the family if the user hadn't synced for the current day. This was required to make that work, but I removed it a few weeks back as it was creating too much complexity.
@@ -0,0 +15,4 @@post session_url, params: { email: @user.email, password: "password" }endendendAppreciate you adding these in!