SQL Error (207): Invalid Column Name 'TABLE_NAME'

When using MS SQL Server, the following error appears.

SQL Error (207): Invalid Column Name 'TABLE_NAME'

The following SQL derives the error...

SELECT * FROM "INFORMATION_SCHEMA"."CHECK_CONSTRAINTS" WHERE CONSTRAINT_SCHEMA='dbo' AND TABLE_NAME='...';

SOLUTION Change TABLE_NAME to CONSTRAINT_NAME

This error box pops up every time you click on a MS SQL table.

That's interesting, so not only MySQL does not have that TABLE_NAME column, also MSSQL. I just modified the detection of check constraints, so it's disabled for MSSQL now. See also issue #75 - not yet finished.

after update to (r6204) I got the same error:

/ SQL Error (1109): Unknown table 'CHECK_CONSTRAINTS' in information_schema /

MariaDB 10.3.9

@ansgar - thank you for the fix! Everything works now for me with MS SQL and MariaDB.

My Versions

MariaDB: 10.3.27

MS SQL: 12.0

@ozyrs - download the latest release. That should fix your problem.

@nahonix thank you, but I have r6204, and still have error, even closed HeidSQL and refresh list tables not helping

You did post r6204 in your original post, sorry I did not notice that.

@ansgar - so MySQL would require a check to see if TABLE_CONSTRAINTS exists first before running...SELECT * from INFORMATION_SCHEMA.CHECK_CONSTRAINTS?

Yes, this is a different error - ozyrys does not have the whole table IS.CHECK_CONSTRAINTS in MariaDB 10.3.9. Sigh, I'll go and add another version check.

Next build will

• dynamically check the existence of tables in information_schema
• not try to run the constraint detection if CHECK_CONSTRAINTS table does not exist
• silently fail once when that table exists, but does not have the TABLE_NAME column

These modifications will a) fix both of your issues, and b) remind me of incompatible detection of check constraints on many servers.

@ansgar thank you! I confirm it work now :)