[MDEV-6760] init script ignored lower_case_table_names in the mariadb section Created: 2014-09-19  Updated: 2014-10-11  Due: 2014-10-10  Resolved: 2014-10-11

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.0.13
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: VAROQUI Stephane Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

After a fresh install on centos 6.5 via yum
lower_case_table_names=1 set in /etc/my.cnf.d/server.cnf in [mariadb-10.0] section.

After restart the variable is not set !

setting lower_case_table_names in the [mysqld] section works



 Comments   
Comment by Elena Stepanova [ 2014-09-24 ]

Works for me:

$ cat /etc/my.cnf.d/server.cnf 
#
# These groups are read by MariaDB server.
# Use it for options that only the server (but not clients) should see
#
# See the examples of server my.cnf files in /usr/share/mysql/
#
 
# this is read by the standalone daemon and embedded servers
[server]
 
# this is only for the mysqld standalone daemon
[mysqld]
 
# this is only for embedded server
[embedded]
 
# This group is only read by MariaDB servers, not by MySQL.
# If you use the same .cnf file for MySQL and MariaDB,
# you can put MariaDB-only options here
[mariadb]
 
# This group is only read by MariaDB-10.0 servers.
# If you use the same .cnf file for MariaDB of different versions,
# use this group for options that older servers don't understand
[mariadb-10.0]
lower_case_table_names=1

$ mysql -uroot
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 3
Server version: 10.0.13-MariaDB MariaDB Server
 
Copyright (c) 2000, 2014, Oracle, SkySQL Ab and others.
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
MariaDB [(none)]> select @@lower_case_table_names;
+--------------------------+
| @@lower_case_table_names |
+--------------------------+
|                        1 |
+--------------------------+
1 row in set (0.00 sec)

Could you please double-check, maybe restart didn't work, or something?

Comment by VAROQUI Stephane [ 2014-09-24 ]

Thanks Elena i'll point this to our client, for him to re-check.

Comment by Elena Stepanova [ 2014-10-11 ]

Closing for now as 'Cannot Reproduce', please comment to re-open if you get new information.

Generated at Thu Feb 08 07:14:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.