If you are in the 'drawer' and browsing the structure and hit Enter on a table, it brings up a list of 'helpers'
Choosing a helper fails if the database name does not match the database name from the connection config. It is valid not to specify a db name in the config, but that then means you can't use any of the databases because of this issue.
I think two improvements would be:
the helper - which is executed in the context of having selected a database from the drawer - should know to work on the database selected in the drawer.
where a db is pre-selected in the config, it should be easier to get to it. It is still useful to show all dbs reachable with the connection, but some way to show the one pre-selected in config would be helpful. On a host with 100 databases, it would be nice not to have to search for something that's specified in config. Perhaps the selected one could simply be sorted to the top of the list?
"logic" for helpers knowing database names is there, but i was too lazy to support it in a few drivers.
this plugin basically grew out of my first intended small scope - my idea was just ine database per connection and to restrict it by it. This changed at some point and I plan on supporting multiple dbs on the same connection as you suggested.
TL;DR I plan on suporting multiple dbs and addressing helper problem, but it will probably take some time :)
If you are in the 'drawer' and browsing the structure and hit Enter on a table, it brings up a list of 'helpers'
Choosing a helper fails if the database name does not match the database name from the connection config. It is valid not to specify a db name in the config, but that then means you can't use any of the databases because of this issue.
I think two improvements would be:
Thanks!