Repository navigation
Release 2.3.0 - #262
Merged
Merged
Release 2.3.0#262
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
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.
Why
Ships #259, #260 and #261 to users: named parameters in prepared statements, a bounded
ping, and theset_timeouts!deadline fix.Bumps the version to 2.3.0. It is a minor release because it adds features. Included since 2.2.2:
Added
DBInterface.prepare(conn, "INSERT INTO t VALUES (:id, :name)")sends each:nameto the server as?, andDBInterface.executebinds aNamedTuple, or anAbstractDictwithSymbolorStringkeys, by name. A name can appear more than once, and a missing name throwsMySQLInterfaceErrorbefore anything is sent.DBInterface.executemanybinds each row of aNamedTuplebatch by name. Statements with?markers behave as before. (Named Parameters Does not Work for prepare() function #207, Support named parameters in prepared statements #261)MySQL.ping(conn; timeout)bounds the whole ping bytimeoutseconds. When the time runs out, the connection is closed andMySQL.Protocol.TimeoutErroris thrown, so a connection pool's health check no longer waits minutes on a network that drops packets.ping(conn)behaves as before. (A boundedping(conn; timeout)#258, Add a timeout keyword to MySQL.ping #260)Fixed
MySQL.Protocol.set_timeouts!(s, 0, 0), the deadline armed by the previous timeouts stayed in place, so a later statement failed withTimeoutErrorand the connection closed. Setting the timeouts now clears the old deadlines. (Protocol.set_timeouts!(s, 0, 0)leaves the last armed read/write deadline in force; the next statement fails withTimeoutError#257, Clear transport deadlines when set_timeouts! changes the timeouts #259)Changed
sql_mode=ORACLE, where:xis the server's own positional marker, aNamedTuplenow binds by name instead of in field order. A Tables.jl row passed as the parameters there throwsMySQLInterfaceError; pass a tuple or vector to bind by position. (Support named parameters in prepared statements #261)🤖 Generated with Claude Code