forked from blackbeam/mysql_async
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Bump/v0.33.0 #10
Closed
Closed
Bump/v0.33.0 #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rumentation Add support for tracing
…arams Introduce SSL-related query params (fix blackbeam#225)
This prevents internal queries like `SELECT @@max_allowed_packet` from showing up in user tracing unless tracing level TRACE is allowed.
Also move set_len(0) into put() and use Vec::shrink_to().
Allow specifying an initial pooled buffer size
…-conn-queries Don't emit INFO spans for administrative queries
…s-spans Record errors from routines in tracing spans
Capabilities setup
Update to lru v0.10.0
Prepare 0.32.0 release
…eplacement Replace crate priority_queue with keyed_priority_queue
Do not read unnecessary settings in Conn::read_settings
I found a spelling-mistake in the doc comments where `Executes` is misspelled as `Exectues` of the following methods: `exec_batch()` `exec()` `exec_first()` `exec_map()` `exec_fold()` `exec_drop()`
A leading forward slash in the connection URL makes get_opts_db_name_from_url set db_name to Some("") rather than None. This makes code pulling the db from config requiring extra checks as db_name.is_some() will evaluate to true. Empty database parameter is invalid for MySQL.
Usability improvement: leading forward slash empty database
Fixed spelling mistake in doc-comments
* The TTL, if set, forces connections to be disconnected, even overriding the minimum pool size constraint. * The TTL can be combined with a random jitter value to prevent all connections closing at the same time. * This enables gradual connection migration and regular connection recycling when CONN_RESET on return to pool is not desired.
Option to set an absolute TTL for connections
…rest of the project
add ResultSetStream types export
Release 0.33.0
Signed-off-by: csh <[email protected]>
L-jasmine
force-pushed
the
bump/v0.33.0
branch
from
December 21, 2023 10:13
98f3569
to
27c65f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.