MySQL Bugs: #114637: Mac new intall will not honor workbench options file and crashes in pref.pane

Bug #114637	Mac new intall will not honor workbench options file and crashes in pref.pane
Submitted:	12 Apr 2024 16:20	Modified:	25 Apr 2024 12:55
Reporter:	Sean Redenbaugh	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S1 (Critical)
Version:	8.1.0-arm64	OS:	MacOS (sonoma)
Assigned to:		CPU Architecture:	ARM (M2)
Tags:	crash, mac, Options, preferences

Description:
On a brand new mac running Sonoma, M2 chip, I am trying a brand new install of MySQL server community 8.1.0 and Workbench 8.0.33.

It is installed, and working, however it is not honoring the config file and if I make a change a change to it in workbench, as soon as I restart MySQL server - the change resets.  And the bigger issue - if I go the preferences pane for MySQL and choose a file path at all in the 2nd tab - SQL server crashes.  Won't start.  You cannot choose a file at all or it will crash.

I've tried editing the file manually at /etc/my.cnf and if I do - the changes are not recognized.  

How to repeat:
Enter a path in preferences pane - sql server won't start

Make a change to the config file in workbench, restart SQL server - change gone

Suggested fix:
no idea

Hello Sean Redenbaugh,

Thank you for the bug report.
What changes have you done to config file in workbench?
May I kindly request you to launch workbench under debug mode (--log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html)?

Regards,
Ashwini Patil

We are trying to get rid of the flag for only_full_group_by

We change it in workbench - and it works.  Until we stop/restart the sqlserver.  Then it blows it away and is back to normal.  Also - in the mac system preferences pane - if we check the box to give a path to a configuration file - the server will not start - just pops back to a red dot.  No matter what - even on a fresh install.

Hello Sean Redenbaugh,

Thank you for the details.
To tell MySQL to accept the query, you can use the ANY_VALUE() function. Alternatively, disable ONLY_FULL_GROUP_BY. 
For more info, please see here https://dev.mysql.com/doc/refman/8.0/en/group-by-handling.html

Also, can you please provide unaltered workbench log file along with screenshot of the issue?

Regards,
Ashwini Patil

I will try to provide screenshots, but I am super annoyed that I state a problem "when we get rid of group by in config it doesn't take", and then you come back with "try eliminating the flag for group by" when I just said we do that and then restarting the server wipes the change out.  It's like no one even is listening.

Version of Mysql - works only when config file is not selected (pic to come)

Attachment: Screenshot 2024-04-16 at 10.57.35 AM.png (image/png, text), 46.20 KiB.

Hello Sean Redenbaugh,

Thank you for the screenshots and other details.
As seen in screenshot:
Server version 8.1.0 is not supported by Workbench configuration file management tool.
Kindly use MySQL Server 8.0 to connect with Workbench 8.0.33.

Also, this is duplicate of Bug #112403.

Regards,
Ashwini Patil

It is not a duplicate of that issue.  That is one piece of what is going on. Did you even look at all the screenshots?  Tell me how the sql server fails and turns back red if you check that box in the other screenshot or give it a path?  Why is that happening?  I went to all that trouble explaining and showing screenshots and you didn't even address it.  How does that have anything to do with workbench?  I'll install the version you suggested today.

There are also about 30 versions of 8.0 - goes all the way to 8.0.35.
I guess I'll try that one.  Does it matter?

Installed 8.0.35 - no longer get the message about incompatibility - but the issue still persists.  I cannot in any way get the DB to use a my.cnf file!

I apprectiate being forgotten about.  And the lack of reading everything.  And the quick attempt to just say this was a duplicate so you could move on.  Very disappointed in MySQL.  We will be looking at other options.  Thanks for all your 'help' - still won't read the file - even on a fresh install.  But I'm done working with people who don't care - time to go to google cloud or some other SQL server.