Skip to content

Added ability to set Json prepared statement parameter.#43

Open
gilius38 wants to merge 67 commits intokrummas:masterfrom
gilius38:master
Open

Added ability to set Json prepared statement parameter.#43
gilius38 wants to merge 67 commits intokrummas:masterfrom
gilius38:master

Conversation

@gilius38
Copy link
Contributor

@gilius38 gilius38 commented Nov 7, 2017

Also integrated old commit 3238a00 that
was never pulled in

gilius38 and others added 30 commits November 7, 2017 18:00
Also integrated old commit 3238a00 that
was never pulled in
appropriate error message) upon 'too many connections' or other
connection errors
Now handling backquotes the same way single and double quotes are handled
- Enabled TLS 1.1 and 1.2 support
- Upped version to 1.5.3-snapshot
(AuthMoreData) in sha2 plugin
Adding ability to hex dump raw packets to ease debug
. 1.5 sources deprecation -> went 1.6
. https://bugs.openjdk.java.net/browse/JDK-8212233 bug workaround
connection phase could hang forever reading welcome packet. Applied the
same logic and value as "connectTimeout" using setSoTimeout on  reading
handshake phase packets (only) to avoid blockage
incompatible charset / collation, for example, if the connection is
using :
set names 'utf8' collate 'utf8_unicode_ci'

then next call to getColumns would fail to fetch columns definition with
: Illegal mix of collations (utf8_general_ci,COERCIBLE) and
(utf8_unicode_ci,COERCIBLE) for operation '='
Don't translate provided query bytes into string until it is needed
(lazy translation)
- Implemented batch to send every query altogether
- Fixed some error messages (only displaying start of the queryin case
of long query, ...)
This was failing with edge cases (when the length of the query is near
the max network packet size, ie. 0xFFFFFF)
Now it will return just an empty result.
(which could fail with String index out of range)
delays transferring small amount of data (especially on SSL handshake)
gilius38 and others added 30 commits May 19, 2021 18:15
like / pattern matching queries that can behave badly under some
circumstances
closing the SSL connection could lead to a deadlock when the remote
server connection was not responding
.Enabling TLSv1.3 protocol by default
.Fixed java source/target version to 1.8 since 1.6 was EOL long ago
connecting to MySQL.
This allows special characters in DB name like '-'
connecting to MySQL.
This allows special characters in DB name like '-'
aliases found in the configured keystore. This typically allows seamless
MySQL server cert rotation.
Change required to dismiss java 1.6 support, now 1.8+ required
Also added loglevel checks before calling logger.fine[st]()
unnecessarily.
interal to the connection function since these will only be used in case
of reconnection/alias-retry
together with its Apache 2 license that has to be kept as-is
Strings could be very large and could generate OOM errors. Now handling
streaming of these string parameters.
- fixed a couple of issues that were not handled previously
- added a junit test
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.

3 participants