Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.3
    • Fix Version/s: 10.0.5
    • Component/s: None
    • Labels:
    • Environment:
      Ubuntu/Presice/LXContainer

      Description

      ConnectSE ships with special columns. I.e. tabid and servid.
      Given:

      CREATE TABLE `federatedconnect` (
        `id` int(11) NOT NULL,
        `id2` int(11) DEFAULT NULL
      ) ENGINE=CONNECT DEFAULT CHARSET=latin1 `TABLE_TYPE`='mysql' `TABNAME`='aha' `DBNAME`='test' `OPTION_LIST`='user=me,host=10.0.3.191'
      

      We build a table_type=tbl table with the special column tabid

       CREATE TABLE `federatedconnect_s` (
        `server` char(20) NOT NULL DEFAULT 'nix' `special`=tabid,
        `id` int(11) NOT NULL,
        `id2` int(11) DEFAULT NULL
      ) ENGINE=CONNECT DEFAULT CHARSET=latin1 `TABLE_TYPE`='tbl' `table_list`='federatedconnect' 
      
      MariaDB [test]> select * from federatedconnect_s limit 1;
      +------------------+----+------+
      | server           | id | id2  |
      +------------------+----+------+
      | federatedconnect |  5 | NULL |
      +------------------+----+------+
      1 row in set (0.00 sec)
      

      Ok that works as expected. Now use the special column servid.

      CREATE TABLE `federatedconnect_s` (
        `server` char(20) NOT NULL DEFAULT 'nix' `special`=servid,
        `id` int(11) NOT NULL,
        `id2` int(11) DEFAULT NULL
      ) ENGINE=CONNECT DEFAULT CHARSET=latin1 `TABLE_TYPE`='tbl' `table_list`='federatedconnect' 
      
      MariaDB [test]> select * from federatedconnect_s limit 1;
      ERROR 1296 (HY000): Got error 174 'Column *SERVID not found in federatedconnect_s' from CONNECT
      

      So servid is not there to be used.
      Regards
      Erkan

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            SERVID is documented here: https://kb.askmonty.org/en/using-connect-virtual-and-special-columns/ , and also mentioned here: https://kb.askmonty.org/en/connect-table-types-using-the-tbl-and-mysql-types-together/

            If it's not supported, it should be removed from documentation.

            Show
            elenst Elena Stepanova added a comment - SERVID is documented here: https://kb.askmonty.org/en/using-connect-virtual-and-special-columns/ , and also mentioned here: https://kb.askmonty.org/en/connect-table-types-using-the-tbl-and-mysql-types-together/ If it's not supported, it should be removed from documentation.
            Hide
            bertrandop Olivier Bertrand added a comment -

            Sure enough. The documentation is optimistic as SERVID is not yet fully implemented.
            It will be, I am working on it.

            Show
            bertrandop Olivier Bertrand added a comment - Sure enough. The documentation is optimistic as SERVID is not yet fully implemented. It will be, I am working on it.
            Hide
            bertrandop Olivier Bertrand added a comment -

            SERVID is now implemented. For most table types it returns "Current". For ODBC tables it returns "ODBC".
            It is mainly useful for MYSQL tables. If they are created using a federated server, it returns the federated server name. Otherwise, it returns the host name of the used server.
            Note that for PROXY and PROXY based table, it returns the SERVID of the source table(s).

            Show
            bertrandop Olivier Bertrand added a comment - SERVID is now implemented. For most table types it returns "Current". For ODBC tables it returns "ODBC". It is mainly useful for MYSQL tables. If they are created using a federated server, it returns the federated server name. Otherwise, it returns the host name of the used server. Note that for PROXY and PROXY based table, it returns the SERVID of the source table(s).

              People

              • Assignee:
                bertrandop Olivier Bertrand
                Reporter:
                erkules erkan yanar
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 6 hours
                  6h