AtoM breaks with STRICT_TRANS_TABLES
|Target version:||Release 2.5.0|
|Google Code Legacy ID:||Tested version:|
This may not be urgent but we should probably ask users to stop using STRICT_TRANS_TABLES in MySQL.
I suggest to find a solution for the culture field being truncated and then do some mores testing to evaluate the amount of work needed.
#1 Updated by David Juhasz over 3 years ago
This seems to be related to the use of "ca@valencia" as a language code in the fixtures, e.g.:
There's also two different keys for Brazilian Portuguese: "pt-BR" and "pt_BR", and a non-standard key for "de-CH" (an underscore is the current convention, i.e. "de_CH"). I think these discrepancies point to a bigger discussion about what language codes can be supported in AtoM.
#4 Updated by José Raddaoui Marín about 1 year ago
`ONLY_FULL_GROUP_BY` in SQL mode may also be an issue, see:
#5 Updated by David Juhasz 4 months ago
- Target version set to Release 2.5.0
Targeting for 2.5.0 for Ubuntu 18.04 compatibility. Ubuntu 18.04 packages MySQL Server 5.7.24 which has STRICT_TRANS_TABLES on by default (Ref: https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_strict_trans_tables).