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

Cache and reuse generated tokens. #5

Merged
merged 2 commits into from
Dec 16, 2024
Merged

Conversation

floor114
Copy link
Owner

Closes #3

@floor114 floor114 force-pushed the cache-generated-passwords branch from b9dfdef to 9789299 Compare December 16, 2024 14:38
@floor114 floor114 mentioned this pull request Dec 16, 2024
@floor114 floor114 merged commit e2c163f into main Dec 16, 2024
5 checks passed
@matt-domsch-sp
Copy link

Since this requires seting reconnect false to the low-level mysql C connection layer, what is the behavior when a database cluster fails over from primary to replica, promoting the replica, and a previous connection no longer works? Today, without using thsi gem, the low-level driver reconnects automatically, invisible to the application. I'm concerned that not setting this, that activerecord won't automatically reestablish a connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature request: reuse password tokens for their lifetime
2 participants