Bug #91539 Error in config file lower_case_table_names has a float instead a integer

• Submitted: 3 Jul 2018 15:22
• Modified: 4 Jul 2018 9:00
• Reporter: Patrick Ciesielski
• Status: Duplicate
• Category: MySQL Server: Installing
• Severity: S3 (Non-critical)
• Version: 8.0.11
• OS: Any
• CPU Architecture: Any

[3 Jul 2018 15:22] Patrick Ciesielski

Description:
If anybody instal MySql with the installer 8.0.11 the configfile is wrong.
The parameter lower_case_table_names get a float value (0.0) instead an integer value (0).

If I fix this in the configfile the changes will be overwritten because the installer write the configfile new.

There are changes in lower_case_table_names variable at release:

https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-11.html

How to repeat:
Download the newest version of the installer and install MySQL Server. Than check the my.ini.

[3 Jul 2018 15:29] Patrick Ciesielski

Beginning configuration step: Initializing Database
Attempting to run MySQL Server with --initialize-insecure option...
Starting process for MySQL Server 8.0.11...
Starting process with command: C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 8.0\my.ini" --console --initialize-insecure=on...
2018-06-26T08:44:42.036600Z 0 [ERROR] [MY-011071] [Server] Unknown suffix '.' used for variable 'lower_case_table_names' (value '0.0')
2018-06-26T08:44:42.036600Z 0 [ERROR] [MY-011071] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: Error while setting value '0.0' to 'lower_case_table_names'
2018-06-26T08:44:42.036600Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-06-26T08:44:42.036600Z 0 [Note] [MY-010120] [Server] Binlog end
Process for mysqld, with ID 3232, was run successfully and exited with code 1.
Failed to start process for MySQL Server 8.0.11.
Database initialization failed.
Ended configuration step: Initializing Database

[4 Jul 2018 9:00] Chiranjeevi Battula

Hello Patrick Ciesielski,

Thank you for the bug report.
This is most likely duplicate of Bug #91476, please see Bug #91476

Thanks,
Chiranjeevi.