You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I clicked on a table in HeidiSQL's tree view and got two popups telling me that the table doesn't exist. After dismissing them, the cursor became a spinning circle, which implies that the program is busy. At first, I thought the program was completely locked up since the circle never went away. To make the cursor reset to regular again, I have to click another table from the tree view.
A minor related issue is that there are two popups instead of one, and the first one says that a "view probably contains an error in its code".
To Reproduce
Open HeidiSQL and connect to a database server
Create a new table called "aaaaa"
Close HeidiSQL
Open HeidiSQL and reconnect to that database server
In a query window, run "DROP TABLE aaaaa"
Click on table aaaaa from the tree view (on the left side of the screen)
Dismiss the two popups warning that the table doesn't exist.
Notice that the cursor remains a spinning circle while hovering over the tree view, results box, or Filter box.
Click another table
Notice that the cursor is back to normal.
Screenshots or Crash reports
couldn't screenshot my cursor, but it looks like this:
The text was updated successfully, but these errors were encountered:
Preconditions
Describe the bug
I clicked on a table in HeidiSQL's tree view and got two popups telling me that the table doesn't exist. After dismissing them, the cursor became a spinning circle, which implies that the program is busy. At first, I thought the program was completely locked up since the circle never went away. To make the cursor reset to regular again, I have to click another table from the tree view.
A minor related issue is that there are two popups instead of one, and the first one says that a "view probably contains an error in its code".
To Reproduce
Screenshots or Crash reports
couldn't screenshot my cursor, but it looks like this:
The text was updated successfully, but these errors were encountered: