mirror of
https://github.com/MariaDB/server.git
synced 2025-10-24 00:27:49 +02:00
1544026443
Fix for this bug and additional improvements/fixes
In detail:
- Remove unicode attribute from several columns
(unicode properties were nowhere needed/tested)
of the table tb3
-> The runnability of these tests depends no more on
the availibility of some optional collations.
- Use a table tb3 with the same layout for all
engines to be tested and unify the engine name
within the protocols.
-> <engine>_trig_<abc>.result have the same content
- Do not load data into tb3 if these rows have no
impact on result sets
- Add tests for NDB (they exist already in 5.1)
- "--replace_result" at various places because
NDB variants of tests failed with "random" row
order in results
This fixes a till now unknown weakness within the
funcs_1 NDB tests existing in 5.1 and 6.0
- Fix the expected result of ndb_trig_1011ext
which suffered from Bug 32656
+ disable this test
- funcs_1 could be executed with the mysql-test-run.pl
option "--reorder", which saves some runtime by
optimizing server restarts.
Runtimes on tmpfs (one attempt only):
with reorder 132 seconds
without reorder 183 seconds
- Adjust two "check" statements within func_misc.test
which were incorrect (We had one run with result set
difference though the server worked good.)
- minor fixes in comments
10 lines
249 B
Text
10 lines
249 B
Text
#### suite/funcs_1/t/innodb_trig_1011ext.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;
|
|
|
|
--source suite/funcs_1/triggers/triggers_1011ext.inc
|