Support the default sql_mode from MySQL 8
|Category:||Data model / ORM|
|Google Code Legacy ID:||Tested version:||2.6|
As a follow-up to #13313, it would be great if AtoM could work with the default
sql_mode in MySQL 8:
- We don't support STRICT_TRANS_TABLES: some work has been done to allow it (see related issue) but we're not there yet. Ideally, we would improve validation and error reporting to be able to inform the user about truncated or invalid data.
- We allow zeros in dates in the event dates and I'm not sure if we allow entire zero dates. Either way, this two modes will join STRICT_TRANS_TABLES in a future MySQL version, so they should be addressed altogether.
- Unknown issue: supporting ONLY_FULL_GROUP_BY may require changes too.
#2 Updated by José Raddaoui Marín over 1 year ago
Running a CSV import with the
skip-nested-set-build option enabled was not working if STRICT_TRANS_TABLES was enabled in the
sql_mode. This has been addressed in:
A bit closer to support the default sql_mode from MySQL 8.
#4 Updated by José Raddaoui Marín over 1 year ago
The following commit removed STRICT_TRANS_TABLES from the sql_mode in the 188.8.131.52 Vagrant box:
We may want to restore it to be able to find the remaining issues in the development/test environments.
#6 Updated by José Raddaoui Marín 12 months ago
It looks like #13144 was not enough to fix the issue creating digital objects without path, see this forum thread: