mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 12:02:42 +01:00
d20a96f9c1
In MariaDB, we have a confusing problem where: * The transaction_isolation option can be set in a configuration file, but it cannot be set dynamically. * The tx_isolation system variable can be set dynamically, but it cannot be set in a configuration file. Therefore, we have two different names for the same thing in different contexts. This is needlessly confusing, and it complicates the documentation. The same thing applys for transaction_read_only. MySQL 5.7 solved this problem by making them into system variables. https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html This commit takes a similar approach by adding new system variables and marking the original ones as deprecated. This commit also resolves some legacy problems related to SET STATEMENT and transaction_isolation. |
||
|---|---|---|
| .. | ||
| r | ||
| t | ||
| disabled.def | ||
| README.txt | ||
Putting testcases here ~~~~~~~~~~~~~~~~~~~~~~ When you work on re-verifying or re-classifying a bug (not fixing it), it's a good idea to put the mtr-parsable '.test' testcase here. Benefits: 1) tests downloaded from the bugs db are sometimes close to mtr-parsable but not completely (for example if they contain /* comment */); when you re-verify or re-classify you run the test so may have to make it mtr-parsable; if you then put it in this suite, the developer who will work on this bug in a few weeks or months will not have to re-do the same download&fix, she/he can instead reuse your work. 2) Others can see how their own work influences many unsolved bugs, by running this suite. If they find that they fix a bug in this suite, we won't later wonder "how come this bug doesn't happen anymore, what fixed it?". 3) One can also run this suite with certain switches to see how they influence unsolved bugs: ./mtr --suite=optimizer_unfixed_bugs \ --mysqld=--optimizer_switch="firstmatch=off" Adding tests to this suite ~~~~~~~~~~~~~~~~~~~~~~~~~~ One test file per bug, named bugNNNNN.test. Put the correct (not current and buggy) result file in r/, so that "[ pass ]" in mtr will mean that a bug looks like fixed. When you have fixed a bug, remove files from this suite. t/bug45219.test is an example.