Beta 13: Cannot disable Auto-Connect

Trying to disable auto-connect in my SSMS connection profile in SQL Assistant, I uncheck the box, press save and close the dialog and come back into the connection profile and it's checked again.

Tried to save it "as administrator" and as a regular user.

Also under targets -> advanced -> auto connection. I cannot change this at all, it's always "None"? Is this a bug? Or can I set each target to connect to a specific connection (usually?). When using MYSQL workbench no matter what I do it asks me to select where to connect (presumably because I cannot set the auto connection?).

This cannot be disabled for SSMS connections. SQL Assistant doesn't open a separate connection in this case, it shares connection with SSMS, that's why that option gets reverted to automatic.

Ok, and thus I cannot have mysql or postres auto connect to any profile because of that? I always get prompted in mysql workbench no matter what and sql assistants editor always defaults to my SQL Server connection.

This depends on MySQL Workbench (MyWB) version installed, type of editor it uses internally, and a number of other factors. SQL Assistant plugin for MyWB attempts to share connection open from MyWB. If it connects to SQL Server, something doesn't click right, and should be investigated. Do you have any MySQL profiles with auto-connect option checked, any of them set to use ADO.NET instead of MySQL native?

Well, that's sort of what lead me to post this. I can't get my MySQL profile in S.A to save the auto-connect checkbox. I assumed maybe that was because only ONE profile could have it and that's my SSMS Profile?

MySQL Workbench doesn't connect to SQL Server, but the SoftTree editor does by default. MySQL workbench always prompts me (usually twice) to connect to the profile. It also asks me to save changes, even if I didn't make any.

MySQL WorkBench is 8.0.36, IIRC. It's the latest available.

The fact S.A tries to "share" the profile may lead me somewhere. Every time the connection manager comes up I have a "ghost" profile using "MYSQL Native" that doesn't actually exist in my DB Connections pane. I am using the ODBC driver, I couldn't find how to make "Native" work and the ADO driver didn't work for me either. So when I start typing "SELECT" the connection pane comes up and I select my profile (usually twice, the pane pops up two times as stated above)

Ok, well I got a copy of libmysql.dll and pointed to it.

I still get the connection prompt every time I open and connect to a server in MySQL workbench. But also now for some reason the autocomplete doesn't see anything past the schemas (eg no tables, views, procedures). If I switch back to the ODBC driver the autocomplete works as one would expect.

libmysql.dll from the 8.0.38 mysql zip file.

I also tried the supplied libMariaDB that comes with SQL Assistant and got the same result.

However, if I use SQL Editor (64-bit) and connect, I can auto-complete past the schema name with the same "Native" connection profile.

	Mindflux wrote:
	MySQL Workbench doesn't connect to SQL Server, but the SoftTree editor does by default. MySQL workbench always prompts me (usually twice) to connect to the profile. It also asks me to save changes, even if I didn't make any.

Right, for some reason it's unable to get a shared connection from MyWB (maybe due to version internal differences) and it opens its own wrong connection based on what it finds first in the settings. That connection makes no sense and I think that old logic is only useful for those who work with a single database. With tools that don't support well documented plugin interfaces, it's a bit of whack a mole game, something is different in every version.

Please close all tools, open SQL Assistant Options dialog from the system tray icon, and check connection settings in DB Options -> DB connection section? Are there MySQL and SQL Server confections with the same name, or incorrect type of DB Type / DB driver combinations, or something else wrong that catches your attention?

The profile names are distinct and seem to be appropriately configured.