Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-203

Empty results if executing mutliple selects in a batch

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.0.7
    • 2.0.19, 3.1.0, 3.0.8
    • General
    • None
    • Server: FreeBSD 11.2 , MariaDB 10.3.10 Client: Windows 10, ODBC 3.0.7

    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?

      Attachments

        Issue Links

          is part of

          Bug - A problem which impairs or prevents the functions of the product. ODBC-169 Empty results or error if executing mutliple selects in a batch

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            Lawrin Lawrin Novitsky added a comment -

            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

            Lawrin Lawrin Novitsky added a comment - 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
            Patrick Dudziak Patrick Dudziak added a comment -

            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.

            Patrick Dudziak Patrick Dudziak added a comment - 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.
            Lawrin Lawrin Novitsky added a comment -

            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

            Lawrin Lawrin Novitsky added a comment - 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
            Lawrin Lawrin Novitsky added a comment -

            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.

            Lawrin Lawrin Novitsky added a comment - 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.
            Lawrin Lawrin Novitsky added a comment - - edited

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

            Lawrin Lawrin Novitsky added a comment - - edited The fix has been pushed to odbc-3.0 in commit 20e0a50
            Lawrin Lawrin Novitsky added a comment - - edited

            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.

            Lawrin Lawrin Novitsky added a comment - - edited 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.

            People

              Lawrin Lawrin Novitsky
              Patrick Dudziak Patrick Dudziak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.