Tatiana A. Nurnberg d49ee1933f Bug#31434 mysqldump dumps view as table ... mysqldump creates stand-in tables before dumping the actual view. Those tables were of the default type; if the view had more columns than that (a pathological case, arguably), loading the dump would fail. We now make the temporary stand-ins MyISAM tables to prevent this. client/mysqldump.c: When creating a stand-in table, specify its type to avoid defaulting to a type with a column-number limit (like Inno). The type is always MyISAM as we know that to be available. mysql-test/r/mysqldump-max.result: add test results for 31434 mysql-test/r/mysqldump.result: mysqldump sets engine-type (MyISAM) for stand-in tables for views now. Update test results. mysql-test/t/mysqldump-max.test: Show that mysqldump's stand-in tables for views explicitly set engine-type to MyISAM to avoid falling back on an engine that might support fewer columns than the final view requires (here's lookin' at you, inno). Also show that this actually has the desired effect by dumping and reloading a view that has more columns than inno supports.		2008-09-11 08:14:19 +02:00
..
.cvsignore
client_priv.h
CMakeLists.txt
completion_hash.cc
completion_hash.h
echo.c
get_password.c
Makefile.am
my_readline.h
mysql.cc
mysql_upgrade.c
mysqladmin.cc
mysqlbinlog.cc
mysqlcheck.c
mysqldump.c
mysqlimport.c
mysqlshow.c
mysqlslap.c
mysqltest.c
readline.cc
sql_string.cc
sql_string.h