Updated dates for INNODB tables

This is somewhat of a guess, but, near as I can see, you are displaying them in the database view for MYSAIM tables. They are not displayed for INNODB tables. I am guessing you are getting that from the timestamp on the physical disk file for MYISAM? Seems to match what I see in the file system.

So, that tells me that perhaps you do not show those for INNODB since those are sometimes stored within the special innodb ibdata files. However, many of us use innodb_file_per_table = 1 and that means there are physical files, and, you can still display the updated dates.

This can be useful for finding tables that people may have created as a work table for some task, but, never dropped it. So, I would like to request you add this feature for when the files actually exist in the file system. It would be very beneficial for us.

The more precise reason for that is that the last update is empty when querying a database per SHOW TABLE STATUS. I think activating innodb_file_per_table does not suddenly activate this value.

I suspect that, even in the case of localhost connections, HeidiSQL always sticks to MySQL API and doesn't try to locate server files in local file system.

Yes, that value is indeed empty, querying the file system is the way to get around this. Wish it could be done, very very useful.

HeidiSQL's only way to communicate with the MySQL server is using the library functions in libmysql.dll, nothing else. Everything what HeidiSQL should do must be doable by some of its functions. And as you can guess, there is no function which directly looks into the server's file system. Feel free to have a look into the documentation yourself.

Well, I have a ssh connection, but, true, it would be unwieldy to add the necessary code. Workbench does do so as it retrieves values from my.cnf, etc. Well, my hope is bug 14374 in mysql 5.7, and, WL6917 to make it persistent. But it will undoubtedly be a while for WL6917.

Workbench is a different beast. Apart from a MySQL client, it includes additional modules such as a server administrator and a visual designer. (Of course, server administrator requires SSH for non-local instances.)