File: aria_tiny.test

package info (click to toggle)
mariadb 1%3A10.11.11-0%2Bdeb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 597,064 kB
  • sloc: ansic: 2,386,076; cpp: 1,663,071; asm: 378,311; perl: 62,203; pascal: 38,769; sh: 37,071; java: 33,919; sql: 19,830; yacc: 19,727; xml: 10,509; python: 9,522; ruby: 8,544; cs: 5,855; makefile: 5,793; ada: 1,700; lex: 1,207; javascript: 1,039; objc: 80; tcl: 73; awk: 46; php: 22
file content (43 lines) | stat: -rw-r--r-- 1,198 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
31
32
33
34
35
36
37
38
39
40
41
42
43
--source include/have_file_key_management_plugin.inc
--source include/have_sequence.inc

SET @aria_encrypt= @@aria_encrypt_tables;
SET global aria_encrypt_tables=1;
#
# MDEV-8022 Assertion `rc == 0' failed in ma_encrypt on dropping an encrypted Aria table
#

create table t1 (i int, key(i)) engine=aria;
insert into t1 values (1);
drop table t1;

#
# MDEV-17913 Encrypted transactional Aria tables remain corrupt after crash
# recovery, automatic repair does not work
#
# We are using a simplifed version of the test here. This works thanks to
# the extended check table code that also checks if LSN's are reasonable.
#

create table t1 (a int primary key, b int, c int, key(b),key(c)) engine=aria;
alter table t1 disable keys;
insert into t1 select seq,seq,seq from seq_1_to_100;
alter table t1 enable keys;
check table t1;
drop table t1;

--echo #
--echo # MDEV CHECK on encrypted Aria table complains about "Wrong LSN"
--echo #

CREATE TABLE t1 (f DATE PRIMARY KEY) ENGINE=Aria;
INSERT INTO t1 (f) VALUES ('1995-01-01'),('2000-01-01');
DELETE FROM t1 WHERE f = '2000-01-01';
OPTIMIZE TABLE t1;
CHECK TABLE t1 EXTENDED;
DROP TABLE t1;

#
# Cleanup
#
set global aria_encrypt_tables=@aria_encrypt;