Information_schema not displaying when connecting to MySql

Avatar
  • updated
  • Answered


Trying to make queries about the structure of my databases using information_schema. I can see and add the database in the databases tab in the connection editor, but they don't show up in list once connected. All the other table show up including performance_schema and sys, as well as my db's.

I'm logging on with root privileges, also tried with an admin user where I specifically all full control over this and all other objects.

I can reference the tables I'm interested in using select statements, which is fine, but I can't see the table visually, can't drag it onto the query editor, etc

Is there a fix for this?

 

 

Avatar
Anonymous

Hello, Peter.

Open the Connection Properties dialog, go to the Databases tab and add "Information_schema" to the list of displayed databases for this connection.

Avatar
Peter

Hi Sergy,

Yes I did so, and it does not show up on the connections pane. You can see from the 3rd window that I have no problems referencing the table by adding sql text, but I cannot manipulate the db visually as I can for every other db.

I am running your latest version (trial version) connecting to mysql 5.7 server 64bit running under windows with a root user. I have a registration, but I haven't yet applied it. Is there anything that happens in the unregistered version that would cause this?

Also, I have a separate bug report in regarding your migrate tool, which you updated, I have not yet had a chance to get back to it, but I will respond shortly. 

I really like your query tool, it is very well done.

Thank you,

Peter

 

This is the statement i placed into the sql text tab, per above

SELECT
information_schema.TABLE_CONSTRAINTS.TABLE_SCHEMA,
information_schema.TABLE_CONSTRAINTS.CONSTRAINT_NAME,
information_schema.TABLE_CONSTRAINTS.CONSTRAINT_TYPE,
information_schema.TABLE_CONSTRAINTS.TABLE_NAME,
information_schema.TABLE_CONSTRAINTS.CONSTRAINT_SCHEMA,
information_schema.REFERENTIAL_CONSTRAINTS.MATCH_OPTION,
information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE,
information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE,
information_schema.REFERENTIAL_CONSTRAINTS.TABLE_NAME AS TABLE_NAME1,
information_schema.REFERENTIAL_CONSTRAINTS.REFERENCED_TABLE_NAME,
information_schema.REFERENTIAL_CONSTRAINTS.UNIQUE_CONSTRAINT_NAME,
information_schema.REFERENTIAL_CONSTRAINTS.UNIQUE_CONSTRAINT_SCHEMA,
information_schema.REFERENTIAL_CONSTRAINTS.UNIQUE_CONSTRAINT_CATALOG,
information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME AS CONSTRAINT_NAME1,
information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_SCHEMA AS CONSTRAINT_SCHEMA1,
information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_CATALOG
FROM
information_schema.TABLE_CONSTRAINTS
INNER JOIN information_schema.REFERENTIAL_CONSTRAINTS ON information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME =
information_schema.TABLE_CONSTRAINTS.CONSTRAINT_NAME

 



Avatar
Andrey Zavyalov, PM
  • Answered