trigger casing conflict leads to corrupted data

[Andrew Clancey]

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, the statement runs without error. 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

lower_case_table_names=1
max_allowed_packet=100M
sql_mode='STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION'

# INNODB #
innodb_file_format=Barracuda

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3573