-
Notifications
You must be signed in to change notification settings - Fork 185
Prepared statement cache configuration #225
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
Prepared statement cache configuration #225
Conversation
Added preparedStatementCacheQueries parameter, which controls cache behaviour. When cache limit is reached last used statement is closed before parsing new one. When cache limit is 0 caching of statement is disabled and unnamed statements are used in extended message flow. Negative values stand for IndefiniteStatementCache (default one).
Thank you for your awesome contribution. That's merged and polished now. @Squiry do you want to join this project as a core contributor? That is merging PR's, triaging/closing issues and reviewing PR's of the core contributors? |
Yes, this is normal. This ticket is marked for the |
ok thanks. Looking forward to it ! |
Added preparedStatementCacheQueries parameter, which controls cache behaviour. When cache limit is reached last used statement is closed before parsing new one. When cache limit is 0 caching of statement is disabled and unnamed statements are used in extended message flow. Negative values stand for IndefiniteStatementCache (default one). [#223][#225][#277]
#223
Added preparedStatementCacheQueries parameter, which controls cache behaviour.
When cache limit is reached last used statement is closed before parsing new one.
When cache limit is 0 caching of statement is disabled and unnamed statements are used in extended message flow.
Negative values stand for IndefiniteStatementCache (default one).