File: partition_create_fail.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 (39 lines) | stat: -rw-r--r-- 839 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
 
--source include/have_partition.inc
--source include/have_s3.inc
--source include/have_debug.inc
--source include/have_innodb.inc
--source include/have_sequence.inc
--source create_database.inc

SET @saved_dbug = @@debug_dbug;

# Test failure in create of partition table

CREATE TABLE p0 (
  c1 int primary key,
  c2 int DEFAULT NULL
) ENGINE=InnoDB;
insert into p0 select seq,seq from seq_1_to_10;

SET debug_dbug='+d,failed_create_partitioning_metadata';

--error 1041
alter table p0 engine=s3
  PARTITION BY RANGE (c1)
(PARTITION p0 VALUES LESS THAN (100));

SET debug_dbug=@saved_dbug;

drop table p0;

# If something went wrong, then we have a copy of the .frm file in S3 and
# the following drop table will not fail

--replace_result $database s3
--error ER_BAD_TABLE_ERROR
drop table p0;

#
# clean up
#
--source drop_database.inc