mariadb/BitKeeper/etc/logging_ok

ccarkner@nslinuxw10.bedford.progress.com
heikki@donna.mysql.fi
sasha@mysql.sashanet.com
Created an isolation test for testing isolation levels. BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted 2001-03-27 09:56:45 -05:00			`ccarkner@nslinuxw10.bedford.progress.com`
btr0btr.c Testing bitkeeper innobase/btr/btr0btr.c: Testing bitkeeper BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted 2001-02-22 20:36:56 +02:00			`heikki@donna.mysql.fi`
fixes to get flush test to work only to discover another bug in flush tables - read comments below client/mysqltest.c: fixed bug in send/reap added comments explaining how things work to remove from Monty the temptation to "clean up" my code use a separate pointer for the test line buffer from the query itself - in the case of send they are not the same added memory clean-up for register variables mysql-test/mysql-test-run.sh: added --skip-* option - you can now skip anything you want, good thing to skip is bdb and innobase if you are running only one test to speed up server startup mysql-test/t/flush.test: fixed up flush test after fixing send/reap bug - now found a new bug with flush - I get 1034 incorrect key file error on this - will investigate why, but thought I'd commit the test case first Another case to support Sinisa's assertion that FLUSH TABLES is dangerous and should be avoided :-) BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted 2001-03-23 19:59:30 -07:00			`sasha@mysql.sashanet.com`