File: no_s3.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; 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;