The tree does not show the events

sistemas@'s profile image sistemas@ posted 1 month ago in General Permalink

The tree does not show the events, but if you perform the sql query, the events are in the database

1 attachment(s):
  • eventos-no-mostrados
sistemas@'s profile image sistemas@ posted 1 month ago Permalink

My server is configured correctly, but I don't know why I can't view, edit or delete the events

1 attachment(s):
  • eventos-no-mostrados-2
ansgar's profile image ansgar posted 1 month ago Permalink

Are you sure you are in the database SAI_AGA in the tree?

Please post the contents of the bottom log panel.

sistemas@'s profile image sistemas@ posted 1 month ago Permalink

If I am selecting the SAI_AGA database from the tree, I send an image. I am using MySQL 5.5 on Windows 10

In the second image it looks like NAVICAT if you show it.

2 attachment(s):
  • 11
  • navicat
ansgar's profile image ansgar posted 1 month ago Permalink

Yes, definitely strange, as events should be displayed with at least MySQL 5.1. And your log panel also shows the query for it. Can you please copy the query from your log panel and run it per query tab (SELECT *, EVENT_SCHEMA AS ...)?

ansgar's profile image ansgar posted 1 month ago Permalink

Especially the last two columns in the result are important ("Db" and "Name"), as these are used by HeidiSQL for comparing with the current database.

sistemas@'s profile image sistemas@ posted 1 month ago Permalink

I sent it, what I noticed is that in the query it is in lowercase, while my database is in uppercase (sai_aga, SAI_AGA)

2 attachment(s):
  • 1
  • 2
ansgar's profile image ansgar posted 1 month ago Permalink

Yes, that's the problem. HeidiSQL compares the "Db" value with the current database, which do not match on your side: sai_aga != SAI_AGA.

First thought I just had was: why even compare the Db ? I found I added this Db comparison in commit:49dce8e08b7550cb8b1dbbc6d57f649e77f032c9 to work around MySQL bug 41907. The problem was that MySQL returned events from other schemas. And it was fixed in MySQL 5.1.57, 5.5.12, 5.6.3 and newer.

Now your server is not even affected by the MySQL bug (MySQL 5.5.30 is old, but should have the fix). So I can modify the code in HeidiSQL so it only compares the schema name if the version is older than these. Further on, I will make the comparison case insensitive for older servers.

Code modification/commit 79ce5ed from Ansgar Becker <anse@heidisql.com>, 1 month ago, revision 6785
Fix retrieving MySQL events from the current database on older servers which return a lower case schema name, by turning the comparison case insensitive. Further more, don't compare the schema at all on newer servers with a fix for MySQL bug 41907. See https://bugs.mysql.com/bug.php?id=41907#c360194 and https://www.heidisql.com/forum.php?t=41682
ansgar's profile image ansgar posted 1 month ago Permalink

Please update to the next build (r6785) appearing in Help > Check for updates. The events should be listed with that new build.

sistemas@'s profile image sistemas@ posted 1 month ago Permalink

Great, thank you very much for your help.

ansgar's profile image ansgar posted 1 month ago Permalink

Would be nice to see if it really works for you. Can you verify and post another screenshot?

Please login to leave a reply, or register at first.