[ODBC-317] Some connection attributes treated using wrong data type Created: 2021-06-05  Updated: 2021-06-05  Resolved: 2021-06-05

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.1.12
Fix Version/s: 3.1.13

Type: Bug Priority: Major
Reporter: Lawrin Novitsky Assignee: Lawrin Novitsky
Resolution: Fixed Votes: 0
Labels: None


 Description   

SQL_ATTR_ODBC_CURSORS is SQLULEN, but SQLINTEGER was used
SQL_ATTR_TXN_ISOLATION should be SQLINTEGER, but was treated as SQLULEN. Getting this attribute on 64b system using correct type(SQLINTEGER) could crash the application.

 Comments   
Comment by Lawrin Novitsky [ 2021-06-05 ]

The fix has been pushed as part of the commit 907ef56. The testcase in the 03d0f2d

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