In Percona Server 5.7.14, I discovered that when lower_case_table_names = 1, you can create triggers that have identical names but different casing, e.g. 'triggerOne' and 'triggerone' without issue. If you attempt to drop one of triggers, you can do so successfully. However, running 'SHOW TRIGGERS' will output no triggers, and no triggers will fire on subsequent actions. Additionally, the .TRN files from the trigger you hadn't dropped will remain in the data directory, yet the .TRG file will be gone. Please see the attached sql file for an example. I can provide more information as requested.
my.cnf contents:
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
In Percona Server 5.7.14, I discovered that when lower_case_ table_names = 1, you can create triggers that have identical names but different casing, e.g. 'triggerOne' and 'triggerone' without issue. If you attempt to drop one of triggers, you can do so successfully. However, running 'SHOW TRIGGERS' will output no triggers, and no triggers will fire on subsequent actions. Additionally, the .TRN files from the trigger you hadn't dropped will remain in the data directory, yet the .TRG file will be gone. Please see the attached sql file for an example. I can provide more information as requested.
my.cnf contents:
[mysqld] /var/lib/ mysql /var/lib/ mysql/mysql. sock
datadir=
socket=
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
lower_case_ table_names= 1 packet= 100M 'STRICT_ TRANS_TABLES, NO_ENGINE_ SUBSTITUTION'
max_allowed_
sql_mode=
# INNODB # file_format= Barracuda
innodb_
[mysqld_safe] /var/log/ mysqld. log /var/run/ mysqld/ mysqld. pid
log-error=
pid-file=