mirror of
https://github.com/MariaDB/server.git
synced 2025-01-24 07:44:22 +01:00
89ddc0aa52
Bug#35335 funcs_1: Some tests fail within load_file during
pushbuild runs
Solution: 1. Move files with input data used in load_file,
load data etc.
from suite/funcs_1/<whatever>
to std_data
2. Use for testsuite funcs_1 the server option
--secure-file-priv=<MYSQLTEST_VARDIR>
3. Outfiles have to be stored under MYSQLTEST_VARDIR
+ changes according to WL#4304 Cleanup in funcs_1 tests
- backport of fixes/improvements made in 5.1 to 5.0
The differences between scripts in 5.0 and 5.1 cause
much additional and annoying work during any upmerge.
- replace error numbers with names
- improved comments
- improved formatting
- Unify storage engine names so that result files for
storage engine variants do not differ (some tests)
- remove a script no more used (tests are done in other scripts)
16 lines
368 B
Text
16 lines
368 B
Text
#### suite/funcs_1/t/innodb_triggers.test
|
|
|
|
# InnoDB tables should be used
|
|
#
|
|
# 1. Check if InnoDB is available
|
|
--source include/have_innodb.inc
|
|
# 2. Set $engine_type
|
|
let $engine_type= innodb;
|
|
|
|
# Create some objects needed in many testcases
|
|
USE test;
|
|
--source suite/funcs_1/include/innodb_tb3.inc
|
|
|
|
--source suite/funcs_1/triggers/triggers_0407.inc
|
|
DROP TABLE test.tb3;
|
|
|