[MDEV-6923] Testing for SET STATEMENT .. FOR (MDEV-5231, per-query variables) - Jira

XML

Word

Printable

Details

Type: Technical task
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: N/A
Component/s: Tests
Labels:
- tests

Description

Development task: ~~MDEV-5231~~
docs: http://www.percona.com/doc/percona-server/5.6/flexibility/per_query_variable_statement.html
branch: https://github.com/MariaDB/server/tree/bb-10.1-set-statement

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

mdev6923_win.test
2014-11-03 17:10
99 kB
Elena Stepanova
mdev6923.test
2015-05-19 21:01
98 kB
Elena Stepanova

Issue Links

relates to

MDEV-6940 SET STATEMENT executed after SET GLOBAL does not work

Closed

MDEV-6941 SET STATEMENT affects the value of the GLOBAL variable for the duration of the statement

Closed

MDEV-6942 SET SESSION statement combined with SET STATEMENT has no effect if it's executed for the same variable

Closed

MDEV-6944 SQL_MODEs related to parsing are not applied during execution of the actual statement under SET STATEMENT .. FOR

Closed

MDEV-6945 SET STATEMENT autocommit=... has no effect and causes warnings in the error log

Closed

MDEV-6946 Assertion `0' failed in mysql_execute_command on SET STATEMENT keycache1.key_buffer_size=.. FOR

Closed

MDEV-6948 SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id)

Closed

MDEV-6949 MySQL client does not recognize SET STATEMENT .. FOR USE <db name> as a schema change

Closed

MDEV-6951 Erroneous SET STATEMENT produces two identical errors

Closed

MDEV-6953 SET STATEMENT profiling = .. FOR does not have any effect

Closed

MDEV-6954 SET STATEMENT rand_seedX = ...FOR ... makes the next rand() to return 0

Closed

MDEV-6955 SET STATEMENT tx_isolation = FOR ... inside a transaction is meaningless and cannot have any effect, but is allowed

Closed

MDEV-6956 SET STATEMENT default_master_connection = ... has no effect

Closed

MDEV-6957 SET STATEMENT skip_replication = .. makes the binary log non-replayable

Closed

MDEV-6976 Assertion `! is_set() || m_can_overwrite_status' failed in Diagnostics_area::set_error_status on SET STATEMENT debug_sync

Closed

MDEV-6977 SET STATEMENT query_cache_type apparently has no effect and hence should be disallowed

Closed

MDEV-6996 SET STATEMENT default_week_format = .. has no effect

Closed

MDEV-6997 SET STATEMENT last_insert_id FOR ... does not affect the value written to the binlog

Closed

MDEV-7002 SET STATEMENT sql_log_off has no effect

Closed

MDEV-7006 SET STATEMENT does not work with slow log tuning (long_query_time, log_slow_filter, log_slow_verbosity, log_slow_rate_limit)

Closed

MDEV-7007 SET STATEMENT slow_query_log has no effect

Closed

MDEV-7009 SET STATEMENT min_examined_row_limit has no effect

Closed

MDEV-7012 SET STATEMENT character_set_client, character_set_connection, character_set_filesystem, collation_connection have no effect

Closed

MDEV-7013 SET STATEMENT wait_timeout or interactive_timeout seem meaningless

Closed

MDEV-7015 SET STATEMENT old_passwords has no effect

Closed

MDEV-7018 SET STATEMENT query_response_time_exec_time_debug has no effect

Closed

MDEV-8185 Variables related to query cache are useless in SET STATEMENT

Open

(22 relates to)

Activity

People

Assignee:: Elena Stepanova

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2014-10-24 12:07

Updated:: 2015-05-19 21:31

Resolved:: 2015-05-19 21:31

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.