mirror of
https://github.com/MariaDB/server.git
synced 2025-07-30 16:24:05 +03:00
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.
This commit is contained in:
BIN
mysql-test/std_data/bug49823.CSM
Normal file
BIN
mysql-test/std_data/bug49823.CSM
Normal file
Binary file not shown.
1
mysql-test/std_data/bug49823.CSV
Normal file
1
mysql-test/std_data/bug49823.CSV
Normal file
@ -0,0 +1 @@
|
||||
"2010-02-26 13:32:26","root[root] @ localhost []",2,1,"Query","SELECT 1"
|
|
BIN
mysql-test/std_data/bug49823.frm
Normal file
BIN
mysql-test/std_data/bug49823.frm
Normal file
Binary file not shown.
Reference in New Issue
Block a user