Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6958 10.1 testing
  3. MDEV-6923

Testing for SET STATEMENT .. FOR (MDEV-5231, per-query variables)

Details

    • Technical task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • N/A
    • Tests

    Attachments

      Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6940 SET STATEMENT executed after SET GLOBAL does not work

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6941 SET STATEMENT affects the value of the GLOBAL variable for the duration of the statement

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6942 SET SESSION statement combined with SET STATEMENT has no effect if it's executed for the same variable

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6944 SQL_MODEs related to parsing are not applied during execution of the actual statement under SET STATEMENT .. FOR

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6945 SET STATEMENT autocommit=... has no effect and causes warnings in the error log

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6946 Assertion `0' failed in mysql_execute_command on SET STATEMENT keycache1.key_buffer_size=.. FOR

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6948 SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id)

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6949 MySQL client does not recognize SET STATEMENT .. FOR USE <db name> as a schema change

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6951 Erroneous SET STATEMENT produces two identical errors

        • Trivial - Cosmetic problem like misspelt words or misaligned text.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6953 SET STATEMENT profiling = .. FOR does not have any effect

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6954 SET STATEMENT rand_seedX = ...FOR ... makes the next rand() to return 0

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6955 SET STATEMENT tx_isolation = FOR ... inside a transaction is meaningless and cannot have any effect, but is allowed

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6956 SET STATEMENT default_master_connection = ... has no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6957 SET STATEMENT skip_replication = .. makes the binary log non-replayable

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6976 Assertion `! is_set() || m_can_overwrite_status' failed in Diagnostics_area::set_error_status on SET STATEMENT debug_sync

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6977 SET STATEMENT query_cache_type apparently has no effect and hence should be disallowed

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6996 SET STATEMENT default_week_format = .. has no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-6997 SET STATEMENT last_insert_id FOR ... does not affect the value written to the binlog

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7002 SET STATEMENT sql_log_off has no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7006 SET STATEMENT does not work with slow log tuning (long_query_time, log_slow_filter, log_slow_verbosity, log_slow_rate_limit)

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7007 SET STATEMENT slow_query_log has no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7009 SET STATEMENT min_examined_row_limit has no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7012 SET STATEMENT character_set_client, character_set_connection, character_set_filesystem, collation_connection have no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7013 SET STATEMENT wait_timeout or interactive_timeout seem meaningless

        • Trivial - Cosmetic problem like misspelt words or misaligned text.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7015 SET STATEMENT old_passwords has no effect

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-7018 SET STATEMENT query_response_time_exec_time_debug has no effect

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. MDEV-8185 Variables related to query cache are useless in SET STATEMENT

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Activity

          Ascending order - Click to sort in descending order
          elenst Elena Stepanova added a comment - - edited

          Currently in the "standard" configuration (Linux, normal server with XtraDB, no additional plugins) we have 148 variables which are not read-only and have session scope.
          As of

          bb-10.1-set-statement

          		 
          commit d6981391eb8f904135dfdedb5b90a7592b35e648
          		 
          Author: Oleksandr Byelkin <sanja@mariadb.com>
          		 
          Date:   Thu Oct 30 19:34:54 2014 +0100

          10 are already disabled for SET STATEMENT (cause ER_SET_STATEMENT_NOT_SUPPORTED).

          From the remaining ones, I tried about a half – not like tested them deeply, but at least checked that they do something more than just display their value in a SELECT under SET STATEMENT ... FOR.
          Out of this half, about 2/3 worked and 1/3 didn't.
          This gives enough information for further interpolation.

          Bugs for discovered failures have been filed.
          Most of failures are reproducible with Percona server, but not all of them.
          Bugs reproducible on Percona server are also filed in their LP.

          Attached is a rough test case for all variables (including read-only, global and unsupported). The windows version is the same as Linux minus several variables that do not exist on Windows.

          elenst Elena Stepanova added a comment - - edited Currently in the "standard" configuration (Linux, normal server with XtraDB, no additional plugins) we have 148 variables which are not read-only and have session scope. As of bb-10.1-set-statement commit d6981391eb8f904135dfdedb5b90a7592b35e648 Author: Oleksandr Byelkin <sanja@mariadb.com> Date: Thu Oct 30 19:34:54 2014 +0100 10 are already disabled for SET STATEMENT (cause ER_SET_STATEMENT_NOT_SUPPORTED). From the remaining ones, I tried about a half – not like tested them deeply, but at least checked that they do something more than just display their value in a SELECT under SET STATEMENT ... FOR. Out of this half, about 2/3 worked and 1/3 didn't. This gives enough information for further interpolation. Bugs for discovered failures have been filed. Most of failures are reproducible with Percona server, but not all of them. Bugs reproducible on Percona server are also filed in their LP. Attached is a rough test case for all variables (including read-only, global and unsupported). The windows version is the same as Linux minus several variables that do not exist on Windows.
          elenst Elena Stepanova added a comment - - edited

          There are also plugin variables.

          Query_response_time comes with 1, it doesn't work.
          Spider comes with 80, didn't check them.
          Test_sql_discovery comes with 2, they work.
          Example comes with 4, didn't check them.
          simple_parser comes with 2, didn't check them.
          TokuDB comes with 28, didn't check them.

          Didn't check Cassandra, Mroonga, probably more.

          elenst Elena Stepanova added a comment - - edited There are also plugin variables. Query_response_time comes with 1, it doesn't work. Spider comes with 80, didn't check them. Test_sql_discovery comes with 2, they work. Example comes with 4, didn't check them. simple_parser comes with 2, didn't check them. TokuDB comes with 28, didn't check them. Didn't check Cassandra, Mroonga, probably more.
          elenst Elena Stepanova added a comment -

          Added new Linux test (the Windows one is not updated).

          elenst Elena Stepanova added a comment - Added new Linux test (the Windows one is not updated).
          elenst Elena Stepanova added a comment -

          The feature has not been fully tested, but it's been tested reasonably in accordance to its relative importance.

          elenst Elena Stepanova added a comment - The feature has not been fully tested, but it's been tested reasonably in accordance to its relative importance.

          People

            elenst Elena Stepanova
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.