Bug #25488 mysql_install_db/mysql_create_system_table Failed proc With STRICT_ALL_TABLES
Submitted: 9 Jan 2007 6:27 Modified: 9 Jan 2007 16:45
Reporter: imacat . (Basic Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: Installing Severity:S2 (Serious)
Version:5.0.27 OS:Linux (Linux x86_64)
Assigned to: CPU Architecture:Any

[9 Jan 2007 6:27] imacat .
    Hi.  This is imacat from Taiwan.  mysql_install_db/mysql_create_system_table failed to create the mysql.proc table with sql-mode=STRICT_ALL_TABLES.  It keeps bouncing with:

ERROR 1101 (42000) at line 1: BLOB/TEXT column 'param_list' can't have a default value

    The result is that when installing a new database with mysql_install_db when STRICT_ALL_TABLES is turned on in my.cnf, the "proc" table is missing.

How to repeat:
2 logs are attached below.  One is mysql_create_system_table.  The other is mysql_install_db.  The STRICT_ALL_TABLES is turned on in my.cnf

========== mysql_create_system_table
root@atlas:~# echo "CREATE DATABASE t1;" | mysql
Enter password:
root@atlas:~# mysql_create_system_tables /tmp/t | grep -i "CREATE TABLE" | mysql t1
Enter password:
ERROR 1101 (42000) at line 16: BLOB/TEXT column 'param_list' can't have a default value
========== mysql_install_db
root@atlas:~# mysql_install_db
Installing all prepared tables
Fill help tables

To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h atlas password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at
Support MySQL by buying support/licenses at http://shop.mysql.com
root@atlas:~# chown -R mysql.mysql /var/lib/mysql
root@atlas:~# /etc/init.d/mysql start
Starting MySQL..
root@atlas:~# mysql mysql
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.27

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

| Tables_in_mysql           |
| columns_priv              |
| db                        |
| func                      |
| help_category             |
| help_keyword              |
| help_relation             |
| help_topic                |
| host                      |
| procs_priv                |
| tables_priv               |
| time_zone                 |
| time_zone_leap_second     |
| time_zone_name            |
| time_zone_transition      |
| time_zone_transition_type |
| user                      |
16 rows in set (0.00 sec)

mysql> \q
[9 Jan 2007 10:26] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of Bug #23669
[9 Jan 2007 16:45] imacat .
Indeed.  This is a duplicated to Bug #23669.  I'm sorry that I'm not aware of that at the beginning.

    However, I think you can be more polite saying it.  I looked into other comments for duplicated bug reports, and see no such comment as those you gave me.

    I did have searched the bug database, with the keyword "mysql_install_db", and found no similar ones.  I made some more tests afterwards to the result of "mysql_create_system_table".  Bug #23669 did not appear in the both bug search result.  I was a little surprised of that.

    I spent 2-3 hours to narrow down the problem by myself as possible, in order to help you guys to the best extend.  Please understand I tried to be kind to you MySQL team.  As a system administrator I have to explain all the problems of MySQL to my users, solve them and make them happy.  I'm a little suprised to some trouble MySQL has caused, including unable to restore dump file just dumped from the same server, contents that are cut "silently" "in the past" due to text too long, default database creation fails "silently" with SQL standard mode.  I'm really patient to all these issues for many, many years, which I personally do not think are acceptable for production-use software.  So please be kind to me, too.

    You were doing a great job helping lots of people into the world of free software.  You could be better if you are kind to users that lost clue finding a duplicated bug report.