[CONJ-1032] Compatibility for deprecated arguments is case sensitive now Created: 2022-12-13  Updated: 2022-12-21  Resolved: 2022-12-21

Status: Closed
Project: MariaDB Connector/J
Component/s: configuration
Affects Version/s: 3.0.3, 3.1.0
Fix Version/s: 3.0.10, 3.1.1

Type: Bug Priority: Minor
Reporter: Lucas Collares Favaron Galvao Assignee: Diego Dupin
Resolution: Fixed Votes: 0
Labels: None


 Description   

The arguments useSsl, trustServerCertificate and disableSslHostnameVerification have been deprecated, and now there is a compatibility work around to map them to the new sslMode argument.

The issue is that the method isSet(String, Properties) in Configuration.java that is used for that compatibility is case sensitive, while the 2.x driver was not. All other arguments don't seem to be case sensitive, dealing with it either by using parseBoolean or converting the property value to lower case before checking.



 Comments   
Comment by Diego Dupin [ 2022-12-21 ]

corrected with https://github.com/mariadb-corporation/mariadb-connector-j/commit/1d9bee54ea2f30edecbf005e018d0f208bd87557 and https://github.com/mariadb-corporation/mariadb-connector-j/commit/b1fc3a73119eeb6d5bcf4ec0521edca712eafdcb

Generated at Thu Feb 08 03:20:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.