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

Invalid BIT column value from subselect

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.1.15
    • 3.1.19, 3.2.1
    • General
    • None
    • Windows server 2012 R2

    Description

      ODBC connector returns wrong value of BIT column when it is selected by subselect like:

      CREATE TABLE aaa (x bit);
      INSERT INTO aaa VALUES(0);

      SELECT X, (SELECT x FROM aaa LIMIT 1) FROM aaa;

      result:
      false, true //should be false, false

      Tested via ADODB... Simple test attached...

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31392 Server returns string inerpretation of BIT(n) field value in a subquery

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            marek.srom Marek Šrom created issue -
            marek.srom Marek Šrom added a comment -

            Hello, I'd like to ask if there will be some progress with this issue... Thanks

            marek.srom Marek Šrom added a comment - Hello, I'd like to ask if there will be some progress with this issue... Thanks
            Lawrin Lawrin Novitsky added a comment -

            Sorry, I'll take a look at it this week

            Lawrin Lawrin Novitsky added a comment - Sorry, I'll take a look at it this week
            Lawrin Lawrin Novitsky added a comment -

            I will look more into this, but somehow that is what connector gets from the server. For first column it's \0, for 2nd - "0". You can see the same picture if you run the query in the mariadb command line client.
            I will also talk to server guys. Maybe that is their bug, or maybe that is something expected

            Lawrin Lawrin Novitsky added a comment - I will look more into this, but somehow that is what connector gets from the server. For first column it's \0, for 2nd - "0". You can see the same picture if you run the query in the mariadb command line client. I will also talk to server guys. Maybe that is their bug, or maybe that is something expected
            Lawrin Lawrin Novitsky added a comment -

            And character '0' is rendered as true for bit type since the byte is not zero

            Lawrin Lawrin Novitsky added a comment - And character '0' is rendered as true for bit type since the byte is not zero
            Lawrin Lawrin Novitsky made changes -
            Field Original Value New Value
            Lawrin Lawrin Novitsky added a comment -

            I've workarounded, that I think is the server problem, in the driver

            Lawrin Lawrin Novitsky added a comment - I've workarounded, that I think is the server problem, in the driver
            Lawrin Lawrin Novitsky made changes -
            Component/s General [ 14302 ]
            Fix Version/s 3.1.19 [ 28903 ]
            Fix Version/s 3.2.1 [ 28908 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]

            People

              Lawrin Lawrin Novitsky
              marek.srom Marek Šrom
              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.