Security related: No
Attempted reproductions: N/A (@jnick1)
Successful reproductions: N/A
Reproducabilty: N/A
Steps to reproduce Expected results
Database tables should use the utf8mb4_unicode_ci collation where applicable instead of the latin1_swedish_ci collation. Also, some tables, such as, tblcountry are using the MyISAM storage engine instead of the InnoDB storage engine, causing them to be unusable in the construction of foreign key constraints.
Actual results
Unable to correctly establish foreign key constraints to tblcountry. Fields stored using latin1_swedish_ci may not be able to handle non-English or non-Swedish characters. Changing to utf8mb4_unicode_ci would prevent that potential issue from occurring.
kalevias
commented
6 years ago
Bug Report
Security related: No Attempted reproductions: N/A (@jnick1) Successful reproductions: N/A Reproducabilty: N/A Steps to reproduce
Expected results
Database tables should use the
utf8mb4_unicode_cicollation where applicable instead of thelatin1_swedish_cicollation. Also, some tables, such as, tblcountry are using the MyISAM storage engine instead of the InnoDB storage engine, causing them to be unusable in the construction of foreign key constraints.Actual results
Unable to correctly establish foreign key constraints to tblcountry. Fields stored using
latin1_swedish_cimay not be able to handle non-English or non-Swedish characters. Changing toutf8mb4_unicode_ciwould prevent that potential issue from occurring.Workaround
N/A
Environment N/A