Version 5.1

i've just installed Version 5.1 of HeidiSQL having upgraded from an earler 4.x version. I must say it is all very nice indeed and a big improvement on earlier versions. Well done Anse!

Just one minor niggle. In the previons version, I had a saved session set to load a single database named 'commtesting'. The installation of 5.1 preserved this session but when opening it, I find it opens all databases which begin with the string 'commtesting' - and I have 3 such databases. This is not particularly helpful since it makes it easy to accidentally start working with the wrong database, especially as they are all very similarly named.

I see that the setting for databases to be opened in a session is held in the registry key 'OnlyDBs'. I tried adding a comma at the end of the 'commtesting' string in this registry key value but that did not do the trick.

Maybe there is a way to specify a database as an exact string and if anyone knows how to do this, I would be greateful to know. Otherwise, if the above is unintended behaviour, then perhaps this is something for the To Do list for the next version.

And on the same subject, I can't actually see how to specify the databases to be opened in a new saved session (aside from manually entering them in the registry) so I would be grateful if someone could point me in the right direction here.

Exact db name is a problem, yes. If the regular expression would allow $ at the end that would be solvable but that doesn't seem to be the case. Anyway, should not be such a big problem for you to ignore the 2 others.

> I can't actually see how to specify the databases to be
> opened in a new saved session

Think you mean the old databases input - that was removed, obviously, and moved to below the database tree. No need to specify a database before connecting.

Thanks Anse. I hadn't noticed the database filter.

> Think you mean the old databases input - that was removed,
> obviously, and moved to below the database tree. No need to
> specify a database before connecting.

Actually, I greatly miss that feature. I have 30+ databases defined on my localhost server (copies of my various "live" databases). I like to open just a single database so that I can be sure I'm dealing with the proper database. For that matter, just finding the right database in the long list can be a challenge with similarly named DBs.

If you had groupings (folders) in the Session Manager window, I suppose I could create saved sessions for each local DB. As it is, I have 30+ saved sessions for the live databases. I'd need another 30+ for the local copies. That makes for a lot of saved sessions to scroll through to find the right DB to open.

I hope you'll reconsider removing the option to specify the database to open.

Tim

I should have checked the Issues list before posting. I've added my vote to issue 1228 to add folders into the session manager list. Thanks.

> I hope you'll reconsider removing the option to specify the
> database to open

You did not explain why the current filter combobox does not meet your needs? It does nearly the same as the one on the old session manager.

Perhaps mostly because I'm used to the old way of choosing File, New Session and specifying which DB on the host to open. I missed the Database filter box till now. That's good and I will definitely use it.

Ultimately, though, it would be great to filter when opening. I'm always nervous importing or exporting to a live web site's database that I might put data in the wrong DB. Being able to connect to a specific database even when multiple are available to a user on a given host would ease my worries. I realize the user account still has access to the other DBs. So, maybe in practice this wouldn't actually change anything.

Thanks,
Tim