Is there a way to turn off syntax / error checking while writing queries in MySQL Workbench? It lags almost constantly as I'm typing (presumably to check syntax, as it informs me of errors), and gets even worse if I'm connected to a remote server.
Is there any way to turn this off? I check Preferences and the available documentation and I can't find anything.
I'm using 6.0 Community Edition on OSX Mavericks.
The problem is that MySQL Workbench tries to get help information form the server. With a remote server this can block for a moment which is why it has been redesigned to use a background thread or can be entirely switched off (and be run manually, if necessary). Get the latest MySQL Workbench release for this feature.
Related
Grr - I hate upgrades that break things
I have upgrade MySql Connector/Net to 8.0.31 from I think it was 8.0.28. And also the ODBC (both 32 and 64 bit) to same.
I think this has broken my Excel Power Query connectors which connect a spreadsheet to a database as I'm getting the title error message. Having similar issues with Power BI connectors as well.
I can't trace the inner exception as there is no ability with Excel / Power Query to do this unless I missing something. Other answers talk about this being security stuff but I have no way of changing/altering this.
Even more frustrating is that this message appears on some of my databases but not all.
The underlying MySql database is very old at 5.6.10 (and I have no way of upgrading this)
I'd downgrade back to 8.0.28 (at least it worked) but I'm not sure how feasible of otherwise that is. I get the impression
I can happily query via a SQL tool (e.g. dbeaver or MySQL Workbench) so this is something else.
Any ideas on what I can do to fix this?
Thanks
EDIT:
So I downgrade MySQL Connector t0 8.0.28 (by using Windows Programs and uninstall the various MySQL 'upgraded' component so that downgrade to versions I wanted)
Still had the error. It is very much a security issue and disabling encrypted connection has fixed most of it.
Like to know why this happened as not happy exposing more than I want too.
Phew.
My workaround is to use an odbc connection string.
you'll need the MySQL ODBC driver instead of the .NET that cause the issue.
Download here: https://dev.mysql.com/downloads/file/?id=513647
In powerBI go to 'Get data' and select more. On the bottom of the list of sources is the 'Other' option and about half way is the ODBC.
In case you need an example: https://www.connectionstrings.com/mysql-connector-odbc-5-2/
When I try to export a DB in workbench, it tells me error as in the screenshot below:
As I understood, it wants me to downgrade MySQL, which is currently v5.7.19 came with the wampserver. But when I went to wampserver website I didn't find such MySQL version in older wampserver versions.
Also, when I check updates fro workbench, I am told it is latest version.
If the solution to this problem not by going that way, Please tell me.
In all cases, please help me to solve the problem showed in the screenshot.
That's not an error, but a generic warning Workbench shows when the server is newer than the tools it ships with. This is to let you know that some new features may not be supported. In this particular case the difference should be minimal and you can ignore the message. Alternatively, you can point MySQL Workbench to the mysqldump binary of the current server (using the application settings).
MySQL workbench was working properly till last login(yesterday). When I tried to open an existing connection(today), this error was popped up. I was trying to convert tables from MSSQL to MySQL yesterday.
Detailed error message
MySQL workbench has encountered a problem
Parameter is not valid
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below.
Please make sure to include a detailed description of your actions that lead to this problem.
Thanks a lot for taking the time to help us improve MySQL Workbench!
The MySQL Workbench Team
For future reference, I had the same problem out of the blue with Workbench on Windows 7 so I re-ran MySQL Workbench installer, selected Repair and everything went back to normal.
I guess some update messed up the install.
This is not about the normal login but migration in MySQL Workbench. This part uses separate logins to source and target servers. If your connection to the MS SQL server worked yesterday and you didn't change anything in MySQL Workbench then it is very likely something with your MS SQL server happened. So, someone needs to check if that server is still running properly and can be accessed from your machine.
Okay listen up. Go to your downloads where you had actually downloaded workbench setup right click on it, you will find an option called "Repair", click on it, follow all steps, open your workbench, open your connection now!(Mine is Windows 10)
Note : You can do it by re-installing workbench too! But Repairing the tool is more convenientPFA Image
I just migrated my table to MySQL Server 5.6 in order to get full use of my system memory since XAMPP doesn't allow you to do so because its MySQL is based on a 32-bit arch. I also downloaded MySQL Workbench to control my server. HOWEVER, all of my queries take almost 2 seconds longer than when I had my server running on XAMPP profile. I activate my old server and everything is back to normal...
I checked all of the configuration variables and have set them exactly the same and still nothing changes.
Is there something I'm not seeing understanding here?
Which engines do you use?
How large are your tables?
Maybe this helps
When should database indexes be rebuilt?
I'm trying to get back into PHP and MySQL development since i've found out that MySQL now allows stored procedures. I work with these at work on an Oracle database and use PL/SQL developer to create them. I was looking for a similar sort of interface for MySQL and was pointed in the direction of MySQL workbench. I'm using Xampp as my test server setup and would like to link MySQL Workbench to MySQL on this server however I'm stuck at one of the stages in the installation. I'm trying to create a new server instance and have been successful as far as testing the database connection however on the next page it asks me to set the 'windows configuration parameters' for this machine and failes to discover a MySQL service. I have ensured that both the Apache server and MySQL services are running in Xampp but do not understand why a MySQL service cannot be found and is not being displayed. Has anyone else encountered this issue when trying to use MySQL Workbench and if so, how did you amanage to get it up and running? I'm using Windows 8 and don't know if this is the reason a service isn't being found. I apologise if this is a really simple question with a simple answer however I have only ever used PHPMyAdmin before which is relatively simple to setup.
I have found problems with the packaged *AMP systems. They don't always install things the way other applications expect. e.g. The MAMP system doesn't work well with Python. it's quite easy to install each of Apache, PHP and MySql on Windows (and two of them are already on the Mac and Linux)
If you use the standard MySql install you should have no trouble installing the Workbench, I've done it on both Windows and Mac.
I have found it a bit flakey at times, it won't connect to older server versions and tends to crash when running long scripts. It also doesn't have a great UI for queries, A good program like PLSQL Developer to TOAD would be nice.
The service detection is rather simple. It expects that the service contains "MySQL" in its name. This is planned to be improved later. For now rename your service to something like "MySQL Xampp".