diff options
author | Davi Arnaut <Davi.Arnaut@Sun.COM> | 2010-02-26 09:22:48 -0300 |
---|---|---|
committer | Davi Arnaut <Davi.Arnaut@Sun.COM> | 2010-02-26 09:22:48 -0300 |
commit | b0a1ae09ae12bb3eefda03ff91263a3c860fd49b (patch) | |
tree | 81321b5931ef7c61d9d26c5c4f76f833ab9e1f07 /mysql-test/std_data/bug49823.frm | |
parent | 600a28368916ae07c0694ae090dcba7f2c52b12a (diff) | |
download | mariadb-git-b0a1ae09ae12bb3eefda03ff91263a3c860fd49b.tar.gz |
Bug#49823: mysql_upgrade fatal error due to general_log / slow_low CSV NULL
The problem was that the CSV storage engine does not support NULL
fields, yet in some early 5.1 version the log tables (general_log
and slow_log) were created with null fields. On top of this, when
altering a CSV table column, all fields of the table must be NOT
NULL otherwise the alteration fails.
The solution is to ensure that during upgrade all columns of the
log tables are NOT NULL.
mysql-test/r/log_tables_upgrade.result:
Add test case result for Bug#49823.
mysql-test/std_data/bug49823.CSV:
Sample data for test.
mysql-test/std_data/bug49823.frm:
Add a CSV table which mimics the general_log table, except that
it contains a nullable column.
mysql-test/t/log_tables_upgrade.test:
Add test case for Bug#49823.
scripts/mysql_system_tables_fix.sql:
Ensure that all columns of the log tables are NOT NULL.
Diffstat (limited to 'mysql-test/std_data/bug49823.frm')
-rw-r--r-- | mysql-test/std_data/bug49823.frm | bin | 0 -> 8776 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/mysql-test/std_data/bug49823.frm b/mysql-test/std_data/bug49823.frm Binary files differnew file mode 100644 index 00000000000..527807da1c9 --- /dev/null +++ b/mysql-test/std_data/bug49823.frm |