[ODBC-134] Fetch fails if unbound column contains NULL, and there was some descriptor field set for it Created: 2018-02-04  Updated: 2018-02-11  Resolved: 2018-02-04

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 2.0.15, 3.0.2
Fix Version/s: 2.0.16, 3.0.3

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


 Description   

How to repeat(and it's self-explaining):
ODBC_TEST(unbound_null)

{ SQLHANDLE Ard; OK_SIMPLE_STMT(Stmt, "SELECT NULL"); CHECK_STMT_RC(Stmt, SQLGetStmtAttr(Stmt, SQL_ATTR_APP_ROW_DESC, &Ard, 0, NULL)); CHECK_DESC_RC(Ard, SQLSetDescField(Ard, 1, SQL_DESC_TYPE, (SQLPOINTER)SQL_NUMERIC, 0)); CHECK_STMT_RC(Stmt, SQLFetch(Stmt)); CHECK_STMT_RC(Stmt, SQLFreeStmt(Stmt, SQL_CLOSE)); return OK; }

This bug affects ADO, as similar sequence of actions is possible with CursorLocation adUseClient

 Comments   
Comment by Lawrin Novitsky [ 2018-02-04 ]

The fix and the testcase have been pushed to odbc-3.0(ed92516) and odbc-2.0(d93b0b8)

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