@mattp The explanation of the ONLY_FULL_GROUP_BY switch is explained here. Basically starting in MySQL 5.7.5, the default is enabled. While you can just disable it by removing the option from the MySQL server settings, the better long term solution would be to rewrite the offending queries. This would not only remove the error on default installs but could potentially prevent a source of incorrect data which is why I believe the MySQL folks want it enabled by default. In any case, I have not spent any time hunting down the specific queries but I’ll try to look into that if I can get a chance. The INT issue is as pgr explained above. The only time I see it popping an error up is during the Quick Repair and Rebuild. Without a code modification you will get persistent SQL errors listed in the lower screen that get reported every time you do a QR&R. You could safely ignore them if you knew they were only caused by the reported INT length but a regular user is going to think the manual syncing of the vardefs keeps failing when it really worked. This is all caused by a change starting in MySQL 8.0.17 where it no longer reports the (display) length of an INT as 11. More on this can be found here. This is the relevant part:
Display width specification for integer data types was deprecated in MySQL 8.0.17, and now statements that include data type definitions in their output no longer show the display width for integer types…
My modification just ignores the sync error if it was caused by an INT length validation failure. Now if any SuiteCRM code or 3rd party add-in depended on the reported (display) length of an INT then it could possibly get messed up but I haven’t run into any problems. I’ll need to do some more testing on the upgrade process to make sure it doesn’t use different db validation code.