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

Excel+MariaDB driver not showing table with SYSTEM VERSIONING

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.1.13
    • 3.1.14
    • General
    • None
    • mariadb 10.3.29

    Description

      If I try to connect mariadb on excel 2016 via MariaDB driver (3.1.13), not all tables are listed. Please see screenshot. It seems that only tables with SYSTEM VERSIONING are missing.

      MariaDB [fb_bde]> show tables;
      +--------------------------+
      | Tables_in_fb_bde         |
      +--------------------------+
      | ACL_Orginalfile          |
      | tbl_trait_therm_ACL_Test |
      | tblactivite              |
      | tblistactivite           |
      | tbllaser_proprete        |
      | tbllt3_largeur           |
      | tbllub_acquisition       |
      | tbllub_conf              |
      | tbllub_mesure            |
      | tbllub_msa               |
      | tbllub_reference         |
      | tblpoidsbalance          |
      | vw_lsa_proprete          |
      | vwlub_acquisition        |
      +--------------------------+
      14 rows in set (0.047 sec)
      

      On Excel they are only 13 tables, tblistactivite is missing, it's the only one that have SYSTEM VERSIONING.

      Attachments

        Activity

          deamn Nicolas De Amicis created issue -
          deamn Nicolas De Amicis made changes -
          Field Original Value New Value
          Description If I try to connect mariadb on excel 2016 via MariaDB driver (3.1.13), not all tables are listed. Please see screenshot. It seems that only tables with SYSTEM VERSIONING are missing.
          {{MariaDB [fb_bde]> show tables;
          +--------------------------+
          | Tables_in_fb_bde |
          +--------------------------+
          | ACL_Orginalfile |
          | tbl_trait_therm_ACL_Test |
          | tblactivite |
          | tblistactivite |
          | tbllaser_proprete |
          | tbllt3_largeur |
          | tbllub_acquisition |
          | tbllub_conf |
          | tbllub_mesure |
          | tbllub_msa |
          | tbllub_reference |
          | tblpoidsbalance |
          | vw_lsa_proprete |
          | vwlub_acquisition |
          +--------------------------+
          14 rows in set (0.047 sec)}}

          On Excel they are only 13 tables, tblistactivite is missing, it's the only one that have SYSTEM VERSIONING.
          If I try to connect mariadb on excel 2016 via MariaDB driver (3.1.13), not all tables are listed. Please see screenshot. It seems that only tables with SYSTEM VERSIONING are missing.
          MariaDB [fb_bde]> show tables;
          +--------------------------+
          | Tables_in_fb_bde |
          +--------------------------+
          | ACL_Orginalfile |
          | tbl_trait_therm_ACL_Test |
          | tblactivite |
          | tblistactivite |
          | tbllaser_proprete |
          | tbllt3_largeur |
          | tbllub_acquisition |
          | tbllub_conf |
          | tbllub_mesure |
          | tbllub_msa |
          | tbllub_reference |
          | tblpoidsbalance |
          | vw_lsa_proprete |
          | vwlub_acquisition |
          +--------------------------+
          14 rows in set (0.047 sec)

          On Excel they are only 13 tables, tblistactivite is missing, it's the only one that have SYSTEM VERSIONING.
          serg Sergei Golubchik made changes -
          Description If I try to connect mariadb on excel 2016 via MariaDB driver (3.1.13), not all tables are listed. Please see screenshot. It seems that only tables with SYSTEM VERSIONING are missing.
          MariaDB [fb_bde]> show tables;
          +--------------------------+
          | Tables_in_fb_bde |
          +--------------------------+
          | ACL_Orginalfile |
          | tbl_trait_therm_ACL_Test |
          | tblactivite |
          | tblistactivite |
          | tbllaser_proprete |
          | tbllt3_largeur |
          | tbllub_acquisition |
          | tbllub_conf |
          | tbllub_mesure |
          | tbllub_msa |
          | tbllub_reference |
          | tblpoidsbalance |
          | vw_lsa_proprete |
          | vwlub_acquisition |
          +--------------------------+
          14 rows in set (0.047 sec)

          On Excel they are only 13 tables, tblistactivite is missing, it's the only one that have SYSTEM VERSIONING.
          If I try to connect mariadb on excel 2016 via MariaDB driver (3.1.13), not all tables are listed. Please see screenshot. It seems that only tables with SYSTEM VERSIONING are missing.
          {noformat}
          MariaDB [fb_bde]> show tables;
          +--------------------------+
          | Tables_in_fb_bde |
          +--------------------------+
          | ACL_Orginalfile |
          | tbl_trait_therm_ACL_Test |
          | tblactivite |
          | tblistactivite |
          | tbllaser_proprete |
          | tbllt3_largeur |
          | tbllub_acquisition |
          | tbllub_conf |
          | tbllub_mesure |
          | tbllub_msa |
          | tbllub_reference |
          | tblpoidsbalance |
          | vw_lsa_proprete |
          | vwlub_acquisition |
          +--------------------------+
          14 rows in set (0.047 sec)
          {noformat}
          On Excel they are only 13 tables, tblistactivite is missing, it's the only one that have SYSTEM VERSIONING.

          Thank you for your report!
          Is this something, that didn't happen with previous versions of the driver?

          Lawrin Lawrin Novitsky added a comment - Thank you for your report! Is this something, that didn't happen with previous versions of the driver?
          Lawrin Lawrin Novitsky made changes -
          Fix Version/s 3.1 [ 22900 ]

          It's seems that is the same problem on 3.1.9

          deamn Nicolas De Amicis added a comment - It's seems that is the same problem on 3.1.9

          I have tested with MyISAM, Aria and InnoDB engines and the problem is on all these engines.

          I found a workaround, if I create a view of the system versioned table, the table will be loaded with ODBC

          deamn Nicolas De Amicis added a comment - I have tested with MyISAM, Aria and InnoDB engines and the problem is on all these engines. I found a workaround, if I create a view of the system versioned table, the table will be loaded with ODBC

          It seems that is only the table browser display that don't work: on Windows, with text file .dqy, the file loads data directly into Excel (I found this tip on the web).
          I also tested the same driver ODBC on Linux with unixODBC, it's the same behaviour like Windows: with isql (small tool provided by unixODBC), I can query data, but if I try to browse table with LibreOffice (and ODBC), the tables with SYSTEM VERSIONING aren't visible.

          deamn Nicolas De Amicis added a comment - It seems that is only the table browser display that don't work: on Windows, with text file .dqy, the file loads data directly into Excel (I found this tip on the web). I also tested the same driver ODBC on Linux with unixODBC, it's the same behaviour like Windows: with isql (small tool provided by unixODBC), I can query data, but if I try to browse table with LibreOffice (and ODBC), the tables with SYSTEM VERSIONING aren't visible.
          Lawrin Lawrin Novitsky made changes -
          Component/s General [ 14302 ]
          Fix Version/s 3.1.14 [ 26008 ]
          Fix Version/s 3.1 [ 22900 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 122843 ] MariaDB v4 [ 135568 ]

          People

            Lawrin Lawrin Novitsky
            deamn Nicolas De Amicis
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.