Ifter upgrading Mysql server from 5.5 to 5.7 we found that query 'SET OPTION' is deprecated. We asked our system's developers and they said that they are not plannig any updates to support newer mysql versions.
What can we do now? Is there any way to bypass this deprecated query?
I thinking we can set another server instance with version 5.7 replicating from old server 5.5.
Related
Maintenace tasks such as servers status, client connections etc call come up with the same error.
The version of the server you're trying to connect to is 10.0, which is not supported by Workbench.
Is there a quick hack to allow the use of these with Mariadb 10.04 or 10.06
MySQL Workbench checks for the specific version of the server since each version supports a different set of configuration options. E.g. some 5.6 options must not be set on a 5.5 server.
MariaDB is not officially supported. It could be possible to hack the version check to make it pass with 10.0, but much with the differences between the fork and the original MySQL versions there is a chance that you could run into errors or break your server's configuration. The settings in MariaDB are not 100% compatible.
For that reason it is recommended to use a different tool that has dedicated support for MariaDB.
i have Azure Database for MySQL of version 5.6 in AZURE and i read somewhere that MYSQL support in slave in higher version (5.7) than the master (5.6) but i did not found any reference to it in AZURE doc and did not found any option to configure version when creating replica via AZURE portal , is this possible to configure replica in higher version specifically salve of MYSQL version 5.7 to MYSQL 5.6 master in Azure Database for MySQL ?
Azure Database for MySQL support version 5.6 and 5.7.
You can get all the supported versions and release notes from this document:
Supported Azure Database for MySQL server versions:
MySQL Version 5.6: Refer to the MySQL release notes to learn
more about improvements and fixes in this version.
MySQL Version 5.7: Refer to the MySQL release notes to learn
more about improvements and fixes in this version.
In Azure Database for MySQL,Using dump and restore help you upgrade across MySQL versions. For more details, please see: Common uses for dump and restore
To avoid any compatibility issues, ensure the same version of MySQL is used on the source and destination systems when dumping databases. For example, if your existing MySQL server is version 5.7, then you should migrate to Azure Database for MySQL configured to run version 5.7.
If you don't need to care about the compatibility issues, you can try to use this way to
downgrade and configure the version 5.7 to 5.6.
Hope this helps.
I have installed MySQL 8.0.4, but my Navicat for MySQL can not connect it, the warning is:
1251 - Client does not support authentication protocol
requested by server; consider upgrading MySQL client.
How do I fix it?
From your warning message it looks like that your Navicat do not support MySQL 8.0.4.
Option 1
Just to be clear, the version of MySQL that you updated to 8.0.4 was released at 2018-01-23 and latest version of Navicat was released 2017-05-31 so 99,99% sure that it wont support latest MySQL, so either downgrade to 5.7.x version or just wait next release of Navicat.
Option 2
Check if there is a client for MySQL which is alrady supporting version 8.0.4. Hint here - I'm using SequelPro and it is not supporting it also. Hint #2 MySQL Workbench releasing quite often, meaning the soonish support of latest mysql is quite possible for tham
Option 3
You always have command line client, which is in some cases the best one, especially for learning reasons.
Regards
I am using latest version of workbench The available MySQL version is 5.0.27. Does anybody knows how to update MySQL version?
MySQL Workbench is a client tool that uses an existing server. Both have their own version numbers. The current GA (generally available) version of MySQL Workbench is 6.2.5. For the server there are obviously different versions. You don't need to consider WB when upgrading. Just upgrade your server and WB will happily work with it.
Update
Meanwhile the MySQL group switched to a unique versioning scheme, where all products have the same version number, to indicate which release of a tool works best with which server (e.g. MEB 8.0.15 with MySQL 8.0.15 or MySQL Workbench 8.0.16 with the same versioned server). It makes sense to update all components at the same time to ensure maximum compatibility.
I've scoured the MySql website to see if they have compatibility listings for MySQL Workbench, but have not found anything. Does anyone know if 6.0.x can connect to 5.5.x databases? I'd rather not install and then have to roll back.
MySQL Workbench can connect to most MySQL server versions, but that is probably not the primary question. You should rather ask what minimum version it can work with. MySQL Workbench requires at least MySQL 5.0 and can work with any MySQL server after that (including the new 5.7). Some features like authentication plugin or performance schema support require higher server versions, though.