Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Restore tree status on refresh

bouvrie's profile image bouvrie posted 7 years ago in Feature discussion Permalink
When working with databases and tables in the database pane on the left, sometimes a refresh of the objects is needed to show new tables. Unfortunately, invoking the refresh also causes a reset of all expanded schemas to the state of collapsed.

This could perhaps also be related to the Work Sets Feature Request, in terms of restoring the collapsed/expanded state of specific previously opened schema's/tables.
ansgar's profile image ansgar posted 7 years ago Permalink
I think it's good to keep only the current database expanded. Think of a situation where you have gone through 10 databases, and each of them needs to be reretrieved automatically. When you need it, you click the expand button again which again will fetch the database items.
bouvrie's profile image bouvrie posted 7 years ago Permalink
Ah yes, you're referring to a situation in which one would ideally want to refresh a Work Set (multiple databases), or even all expanded databases.

Personally when I issue a refresh, I'm typically using the "Refresh" context menu option on the specific (current) database. And while doing so I find it annoying having to expand the database again to access the table list and scroll to the new table I was looking for.

In my case I'm frequently dropping and re-creating databases, so I'm refreshing a lot. :)
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
ansgar's profile image ansgar posted 7 years ago Permalink
Please note that you might be one of only a few users who do refreshes such often. For the majority of users I think it's better to have only the current database opened again, not multiple databases.
bouvrie's profile image bouvrie posted 7 years ago Permalink
Sure, I can't think of a situation in which one wants to refresh the current database, and expect another database's tree to be collapsed too. :)
mrforsythexeter's profile image mrforsythexeter posted 1 month ago Permalink

I would like it to maintain current open / collapsed state. Since table refresh doesn't work quiet right, would be good to have this as a fall back.

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




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.