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

ConnectSE: ODBC: do not throw an error on empty CATFUNC=Columns

Details

    Description

      drop table if exists t1;
      		 
      create table t1 engine=connect table_type=odbc catfunc=columns 
      connection='DSN=pgodbc' tabname='t3';
      		 
      select * from t1;

      If the table 't3' does not exist in the remote DSN, the SELECT
      query returns an error:

      ERROR 1296 (HY000): Got error 174 'No data found for table t3' from

      It should return an empty set.

      It does not seem to be useful to send a warning (instead of the error) on every SELECT.
      But sending a warning at CREATE TABLE time could probably be useful, to make
      the user aware that there is no such table on the remoter data source.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          bar Alexander Barkov created issue -
          bar Alexander Barkov made changes -
          Field Original Value New Value
          Description {code}
          drop table if exists t1;
          create table t1 engine=connect table_type=odbc catfunc=columns
          connection='DSN=pgodbc' tabname='t3';
          select * from t1;
          {code}

          If the table 't3' does not exist in the remote DSN, the SELECT
          query returns an error:
          {code}
          ERROR 1296 (HY000): Got error 174 'No data found for table t3' from
          {code}

          It should return an empty set (possibly with a warning).
          		 {code}
          drop table if exists t1;
          create table t1 engine=connect table_type=odbc catfunc=columns
          connection='DSN=pgodbc' tabname='t3';
          select * from t1;
          {code}

          If the table 't3' does not exist in the remote DSN, the SELECT
          query returns an error:
          {code}
          ERROR 1296 (HY000): Got error 174 'No data found for table t3' from
          {code}

          It should return an empty.

          It does not seem to be useful to send a warning (instead of the error) on every SELECT.
          But sending a warning at CREATE TABLE time could probably useful, to make
          the user aware that there is no such table on the remoter data source.
          bar Alexander Barkov made changes -
          Description {code}
          drop table if exists t1;
          create table t1 engine=connect table_type=odbc catfunc=columns
          connection='DSN=pgodbc' tabname='t3';
          select * from t1;
          {code}

          If the table 't3' does not exist in the remote DSN, the SELECT
          query returns an error:
          {code}
          ERROR 1296 (HY000): Got error 174 'No data found for table t3' from
          {code}

          It should return an empty.

          It does not seem to be useful to send a warning (instead of the error) on every SELECT.
          But sending a warning at CREATE TABLE time could probably useful, to make
          the user aware that there is no such table on the remoter data source.

          		 {code}
          drop table if exists t1;
          create table t1 engine=connect table_type=odbc catfunc=columns
          connection='DSN=pgodbc' tabname='t3';
          select * from t1;
          {code}

          If the table 't3' does not exist in the remote DSN, the SELECT
          query returns an error:
          {code}
          ERROR 1296 (HY000): Got error 174 'No data found for table t3' from
          {code}

          It should return an empty set.

          It does not seem to be useful to send a warning (instead of the error) on every SELECT.
          But sending a warning at CREATE TABLE time could probably useful, to make
          the user aware that there is no such table on the remoter data source.
          bar Alexander Barkov made changes -
          Description {code}
          drop table if exists t1;
          create table t1 engine=connect table_type=odbc catfunc=columns
          connection='DSN=pgodbc' tabname='t3';
          select * from t1;
          {code}

          If the table 't3' does not exist in the remote DSN, the SELECT
          query returns an error:
          {code}
          ERROR 1296 (HY000): Got error 174 'No data found for table t3' from
          {code}

          It should return an empty set.

          It does not seem to be useful to send a warning (instead of the error) on every SELECT.
          But sending a warning at CREATE TABLE time could probably useful, to make
          the user aware that there is no such table on the remoter data source.

          		 {code}
          drop table if exists t1;
          create table t1 engine=connect table_type=odbc catfunc=columns
          connection='DSN=pgodbc' tabname='t3';
          select * from t1;
          {code}

          If the table 't3' does not exist in the remote DSN, the SELECT
          query returns an error:
          {code}
          ERROR 1296 (HY000): Got error 174 'No data found for table t3' from
          {code}

          It should return an empty set.

          It does not seem to be useful to send a warning (instead of the error) on every SELECT.
          But sending a warning at CREATE TABLE time could probably be useful, to make
          the user aware that there is no such table on the remoter data source.
          elenst Elena Stepanova made changes -
          Affects Version/s 10.0.10 [ 14500 ]
          elenst Elena Stepanova made changes -
          Summary ConnectSE: ODBC: do not through an error on empty CATFUNC=Columns ConnectSE: ODBC: do not throw an error on empty CATFUNC=Columns
          elenst Elena Stepanova made changes -
          Labels connect-engine
          bertrandop Olivier Bertrand made changes -
          Fix Version/s 10.0.11 [ 15200 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow defaullt [ 31703 ] MariaDB v2 [ 42809 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 42809 ] MariaDB v3 [ 61826 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 61826 ] MariaDB v4 [ 147357 ]

          People

            bertrandop Olivier Bertrand
            bar Alexander Barkov
            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.