Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-14392

CONNECT - Table Type: ODBC - HAVING Clause (Wihtout WHERE and GROUP BY) Has Wrong Results

Details

    Description

      When using CONNECT Engine and Table Type ODBC, when using a HAVING clause for filtering data, wrong results are returned if no WHERE and GROUP BY clause is used.

      For example:

      SELECT
      		 
           *
      		 
      FROM
      		 
           MyTable
      		 
      HAVING
      		 
           MyColumn <> 'MyValue' OR MyColumn IS NULL

      Does not perform a correct filtering. I think that the correct MariaDB behaviour with the HAVING clause shall be that a "local" copy of the table is done in MariaDB Server, bringing the table through ODBC connection, and then filter it in the "local" server itself.

      Thank you,
      Juan

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          bertrandop Olivier Bertrand added a comment -

          Can you elaborate? Trying to execute:

          select * from oremployees where salary > 10000 and commission_pct is null;
          		 
          select * from oremployees having salary > 10000 and commission_pct is null;

          on the sample employees table of Oracle, I get the same result.

          So to try reproduce the bug I should have:

          1. The used ODBC server
          2. The table contains
          3. The table create table
          4. The select statement that gives wrong result
          5. The wrong result

          Thanks.

          bertrandop Olivier Bertrand added a comment - Can you elaborate? Trying to execute: select * from oremployees where salary > 10000 and commission_pct is null; select * from oremployees having salary > 10000 and commission_pct is null; on the sample employees table of Oracle, I get the same result. So to try reproduce the bug I should have: The used ODBC server The table contains The table create table The select statement that gives wrong result The wrong result Thanks.
          Juan Juan Telleria added a comment - - edited

          The SELECT Query Calls a 10 million record table in SQL Server, and gives / shows results little by little, before the query is completed.

          I did not wait when I filled the bug report to see how where results when the hole query executed, because it took more than 2 hours...
          ¿Maybe results aren't filtered until all data is on the local MariaDB Server?

          I will check it out, and try to provide more accurate feedback.

          Thank you,
          Juan

          Juan Juan Telleria added a comment - - edited The SELECT Query Calls a 10 million record table in SQL Server, and gives / shows results little by little, before the query is completed. I did not wait when I filled the bug report to see how where results when the hole query executed, because it took more than 2 hours... ¿Maybe results aren't filtered until all data is on the local MariaDB Server? I will check it out, and try to provide more accurate feedback. Thank you, Juan
          Juan Juan Telleria added a comment -

          I checked it, and it is not a bug.

          Juan

          Juan Juan Telleria added a comment - I checked it, and it is not a bug. Juan

          People

            bertrandop Olivier Bertrand
            Juan Juan Telleria
            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.