File: no_s3.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 (25 lines) | stat: -rw-r--r-- 709 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
 
--source include/have_sequence.inc

let $datadir=`select @@datadir`;

if (`select @@global.s3_secret_key <> "" or @@global.s3_access_key <> ""`)
{
  skip S3 engine options given (probably from command line);
}

#
# Test what happens when we don't have s3 enabled
#
create table t1 (a int, b int) engine=aria select seq,seq+10 from seq_1_to_2;
--error ER_CANT_CREATE_TABLE
alter table t1 engine=s3;
drop table t1;

--copy_file std_data/s3_unique_table.frm $datadir/test/s3_unique_table.frm
--error ER_UNSUPPORTED_EXTENSION
select * from s3_unique_table;
--error ER_UNSUPPORTED_EXTENSION
truncate table s3_unique_table;
--error ER_ERROR_ON_RENAME
rename table s3_unique_table to t1;
drop table s3_unique_table;