Open yuliu opened 4 years ago
I believe PostgreSQL is strict by default basically, an I'm not aware of any options to make it more/less strict. @kawaii may know better though.
MySQL strict mode may be disabled by setting sql_mode
to some combinations of not strict modes, for example:
SET SESSION sql_mode = 'ANSI,ONLY_FULL_GROUP_BY'
This should be useful for normal users who use the merge system but for merge system's developers doing so may not be recommended IMO.
PostgreSQL and SQLite may have equivalently so-called strict mode, but I'm not familiar with them.
Quick search: PostgreSQL: no findings. SQLite: https://sqlite.org/src/wiki?name=StrictMode
Relevant issue: #235. I can't confirm which setting is in effect here, the setting of
sql_mode
when I'm experiencing the problem isSTRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
.A community post complains about
sql_mode
set withonly_full_group_by
: https://community.mybb.com/thread-225560-post-1339852.html#pid1339852Seems MySQL is involving more strict modes along new version releases. So some queries may break the merging in newer MySQL versions.