New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status variables documentation links to dev.mysql.com are invalid #19069
Comments
This is probably due to williamdes/mariadb-mysql-kbs#300 Or that the variable is not known https://github.com/search?q=repo%3Awilliamdes%2Fmariadb-mysql-kbs%20Open_tables&type=code |
williamdes/mariadb-mysql-kbs#300 is for MariaDB and they are working, just with additional redirects. My links are to dev.mysql.com and no link I tried works. I guess MySQL changed their links, so it should be updated in phpMyAdmin. |
Hey, |
Okay, thanks for this info. I may have missed something. I will test on MySQL 5.7 and fix this |
Seems like they exist but only for MariaDB. So the links are not available on MySQL. PS: How to you have such variables, Com_xxx stuff is not showing in my list ? |
Looks like all status variables starting with Thanks for working on this so quickly. I tested it and the link to |
Thank you for confirming, do you know how you did activate the Com_xxx variables? Unfortunately the library does not handle different versions of MySQL in the way where it would send you to the version you are using. It has no knowledge of versions. Only variables. Did you install the composer dev version? |
I did not do anything to enable these variables, it is just a standard installation of MySQL 5.7. I change this in composer.json - "williamdes/mariadb-mysql-kbs": "^1.2"
+ "williamdes/mariadb-mysql-kbs": "dev-main" |
Okay, on the Docker version I do not see them :/ |
Describe the bug
In Status -> Variables clicking the blue question mark icon links to https://dev.mysql.com/doc/refman/5.7/en/open-tables.html
The link should be https://dev.mysql.com/doc/refman/5.7/en/server-status-variables.html#statvar_Open_tables
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Documentation links should be to the correct page.
Screenshots
Server configuration
The text was updated successfully, but these errors were encountered: