[IGNITE-20625] SELECT MIN(column), MAX(column) by ODBC throws exception

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta2
• Fix Version/s: 3.0.0-beta2
• Component/s: odbc
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Igor Sapego
• Reporter: Igor
• Reviewer: Pavel Tupitsyn
• Created: 11/Oct/23 15:06
• Updated: 13/Oct/23 08:20
• Resolved: 13/Oct/23 08:20

Description

Steps to reproduce:

1. Connect to Ignite using ODBC driver (Python).
2. Execute separate queries one by one 

   DROP TABLE IF EXISTS PUBLIC.PARKING;
   CREATE TABLE PUBLIC.PARKING(ID INT, NAME VARCHAR(255), CAPACITY INT NOT NULL, b decimal,c date, CITY VARCHAR(20), PRIMARY KEY (ID, CITY));
   INSERT INTO PUBLIC.PARKING(ID, NAME, CAPACITY, CITY) VALUES(1, 'parking_1', 1, 'New York');
   SELECT MIN(CAPACITY), MAX(CAPACITY) FROM PUBLIC.PARKING; 

Expected result:

Query executed successfully.

Actual result:

The last query throws exception.

The value in stream is not a Binary data : 5

No errors in server log.

Issue Links

• links to: GitHub Pull Request #2687