mariadb/storage
Tatiana A. Nurnberg a7d03bf4ed Bug#31177: Server variables can't be set to their current values
Bounds-checks and blocksize corrections were applied to user-input,
but constants in the server were trusted implicitly. If these values
did not actually meet the requirements, the user could not set change
a variable, then set it back to the (wonky) factory default or maximum
by explicitly specifying it (SET <var>=<value> vs SET <var>=DEFAULT).

Now checks also apply to the server's presets. Wonky values and maxima
get corrected at startup. Consequently all non-offsetted values the user
sees are valid, and users can set the variable to that exact value if
they so desire.
2009-01-12 06:32:49 +01:00
..
archive Merge from mysql-5.1.30-release 2008-11-27 00:02:10 +01:00
blackhole Added "Sun Microsystems, Inc." to copyright headers on files modified 2008-11-10 21:21:49 +01:00
csv Bug#41441 repair csv table crashes debug server 2008-12-29 16:50:51 +04:00
example Merge trift2.:/MySQL/M51/mysql-5.1 2008-03-14 14:41:08 +01:00
federated Fix warnings and bug spotted by gcc-4.3. 2008-12-16 10:12:22 -02:00
heap Fix warnings and bug spotted by gcc-4.3. 2008-12-16 10:12:22 -02:00
innobase Bug#31177: Server variables can't be set to their current values 2009-01-12 06:32:49 +01:00
myisam merged 5.1-main -> 5.1-bugteam 2009-01-05 18:10:20 +02:00
myisammrg Fixed bug#36006: Optimizer does table scan for SELECT COUNT(*) 2008-04-26 02:45:58 +05:00
ndb mysql-test/r/partition.result 2008-11-25 03:04:58 +01:00
Makefile.am