This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
Releases: BoardiesITSolutions/Android-MySQL-Connector
Releases · BoardiesITSolutions/Android-MySQL-Connector
0.52_MySQL8
Fixed issue where COM_QueryResponse would inadvertently detect a MySQ…
0.51_MySQL8
Fixed issue where COM_QueryResponse would inadvertently detect a MySQ…
0.49_MySQL8
Fixed couple of issues with latest version of MySQL 8
- Fixed issue that ztsd compression was not supported (the compression flag being disabled by the client was ignored due to a new server flag)
- Fixed issue when sending query triggered Malformed packet response due to server flag default value being changed so client wasn't disabling.
0.48_MySQL8
Better connection timeout handling - Fixed issue so that the connection timeout doesn't the default Android socket timeout - which can be several minutes - Changed default connection timeout to be 30 seconds - Added new method "setConnectionTimeout" to Connection class to override the default conection timeout in seconds.
0.47_MySQL8
Fixes an issue where if running multiple queries on a database as part of a loop in async (without the returnToMainThread being passed true) the library would deadlock and no further interaction with the database was completed.
0.45_MySQL8
Ensures low level TCP socket issues such as connection timed out don't just throw an exception internal within the library - it will not pass the error up back into the IConnectionResult interface.
0.43_MySQL8
- Fixes issue retrieving BLOB data due to MySQLRow class being reverted by mistake
- Fixes issue retrieving BLOB data when the BLOB data is just a string instead of binary data
- Fixes issue where column type is shown as BLOG instead of BLOB
0.41_MySQL8
- Fixes issue with unnecessary Android:Theme in the manifest file requiring apps to use tools:replace
- Fixes UnsupportedServerException when attempting to connect to MySQl 8.0.21
0.40_MySQL8
Fixes issue where if a BLOB column had an empty string, the column byte would be 0x00 which would be interpreted as a MySQL EOF packet instead of just an empty column, therefore thinking the MySQL result was processed and caused data corruption and/or missing row data.
0.46_MySQL8
Update README.md