Bug #60539 Column mysql.help_topic.url too small.

Submitted: 18 Mar 2011 21:22 Modified: 14 Jan 2013 11:08
Reporter: Сергей Петров Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.5.10 OS:Windows (Seven SP1)
Assigned to: CPU Architecture:Any

[18 Mar 2011 21:22] Сергей Петров
Description:
After MySQL update, I am run %MySQLInstallDir%\share\fill_help_tables.sql script to update build in help. But script ends with error "SQL Error (1406): Data too long for column 'url'". I am investigate it and saw what data files, what comes with server, for table help_topic (%MySQLInstallDir%\data\mysql\help_topic.*) contains truncated data for url column. After that I am increase length for url comlumn to 200 and run script again. Script ends with no error.

How to repeat:
Run script %MySQLInstallDir%\share\fill_help_tables.sql with options what do not allow silent truncation of data.
[19 Mar 2011 1:53] MySQL Verification Team
Thank you for the bug report.

C:\Program Files\MySQL\MySQL Server 5.5>bin\mysql -uroot --port=3309 mysql < share\fill_help_tables.sql
ERROR 1406 (22001) at line 74: Data too long for column 'url' at row 1

C:\Program Files\MySQL\MySQL Server 5.5>
[21 Oct 2011 15:16] MySQL Verification Team
You get this with strict_trans_table sql_mode. Also rpm installer will throw this error.

You can fill the help tables like this:

shell> cd /usr/share/mysql

* login to mysql as root*

mysql> set session sql_mode='';
mysql> \. fill_help_tables.sql

problem is help_topics.url is too small for some in the help file.
[21 Oct 2011 15:19] MySQL Verification Team
not just 5.5, occurs on 5.1 as well either filling manually or installing from rpm with existing my.cnf with that sql_mode...otherwise it's truncated with a warning.
[14 Jan 2013 11:08] Erlend Dahl
Internally worked as a duplicate of Bug#61520, so closing this one.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.