File: pfs_upgrade_table.test

package info (click to toggle)
mariadb 1%3A11.8.2-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, trixie
  • size: 765,428 kB
  • sloc: ansic: 2,382,827; cpp: 1,803,532; asm: 378,315; perl: 63,176; sh: 46,496; pascal: 40,776; java: 39,363; yacc: 20,428; python: 19,506; sql: 17,864; xml: 12,463; ruby: 8,544; makefile: 6,059; cs: 5,855; ada: 1,700; lex: 1,193; javascript: 1,039; objc: 80; tcl: 73; awk: 46; php: 22
file content (30 lines) | stat: -rw-r--r-- 794 bytes parent folder | download | duplicates (5) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 
# Tests for PERFORMANCE_SCHEMA
# Make sure mysql_upgrade does not destroy data in a 'performance_schema'
# database.
# 

--source include/not_embedded.inc
--source include/have_perfschema.inc
--source include/have_innodb.inc

let $MYSQLD_DATADIR= `SELECT @@datadir`;

--echo # Testing mysql_upgrade with TABLE performance_schema.user_table

create table test.user_table(a int);

--copy_file $MYSQLD_DATADIR/test/user_table.frm $MYSQLD_DATADIR/performance_schema/user_table.frm

# Make sure the table is visible
use performance_schema;
show tables like "user_table";

--source suite/perfschema/include/upgrade_check.inc

# Make sure the table is still visible
show tables like "user_table";

use test;

--remove_file $MYSQLD_DATADIR/performance_schema/user_table.frm
drop table test.user_table;