[ODBC-203] Empty results if executing mutliple selects in a batch Created: 2018-11-28  Updated: 2018-12-02  Resolved: 2018-12-02

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.0.7
Fix Version/s: 2.0.19, 3.1.0, 3.0.8

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

Server: FreeBSD 11.2 , MariaDB 10.3.10 Client: Windows 10, ODBC 3.0.7

Issue Links:
PartOf
is part of ODBC-169 Empty results or error if executing m... Closed

 Description   

This issue sadly still presists. The rowcount is now correct, but the content is still empty.

To clarify in case 3/4 if the table contains numerical values it works, but the results return empty strings for strings and text.

Same for the last two cases, the results are empty for strings/text and numerical values cause a FormatException. I see that the commit https://github.com/MariaDB/mariadb-connector-odbc/commit/bfb78c0 checks the for the correct rowcount but not the content.

Any ideas what could be causing this?

 Comments   
Comment by Lawrin Novitsky [ 2018-11-28 ]

Hello and thanks for the report.
True that the testcase does not check values. But it does output them. And (correct) values are there. Thus there must be something else causing your problem.
Do you mean that exact cases described in ODBC-169 are still failing for you?

p.s. But you are right, It's probably better to add values check to the testcase

Comment by Patrick Dudziak [ 2018-11-28 ]

Yes, i am talking about the exact same cases as described in ODBC-169. They do work now, but the results are just empty strings, only numerical values work for the sample tables. Hence why a testcase with only integer values might work even when checking the content.

For the last 2 cases from ODBC-169 where we use data from the INFORMATION_SCHEMA, numerical values return FormatException. Strings are just empty again.

Maybe test with VARCHAR/TEXT/BLOB the content of the fields.

Thank you for your fast reponse.

Comment by Lawrin Novitsky [ 2018-11-28 ]

Well, the testcase already has the varchar field, and it's not empty either. And correct values are returned.
I think I also need to take another look in your traces in ODBC-169

Comment by Lawrin Novitsky [ 2018-11-30 ]

Ok, I will verify everything once again, but looks like fetching data as wide strings makes difference here. That is strange, atm I can't imagine how that can cause that. But will see.

Comment by Lawrin Novitsky [ 2018-12-02 ]

The fix has been pushed to odbc-3.0 in commit 20e0a50

Comment by Lawrin Novitsky [ 2018-12-02 ]

The fix does not care about FormatException for numeric fields problem, but looking at the traces for last 2 cases in ODBC-169, I can imagine, that it is also fixed.

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