[ BUILD # : 200810080330 ]
[ JDK VERSION : 1.6.0_07 ]
Using another tool to connect to a MySQL server such as SQLYog
(www.webyog.com), we can connect to a MySQL server without have to
specify a database.
Also in reality, we don't always have the knowledge of the existing
databases in a MySQL server.
Selection of a database when connecting to a MySQL server should be
You can register MySQL server and then expand it's node and You'll see all existing databases and connect to every of
them. Or this way doesn't fit You for some reason?
Created attachment 71524 [details]
New database connection dialog
Sorry, for not being specific enough.
What I meant was the first time we need to register/connect to a MySQL server.
(on the Services tab, we right click on a MySQL node and then Connect Using)
I attached the screenshot.
In NetBeans, by starting MySQL, you are connected without specifying a database. Maybe just the terminology differs.
If you want to connect to a database but don't know the databases available:
1) Start MySQL
2) Expand the MySQL node
3) Select a database, right-click then choose Connect...
correction, once you start MySQL, there is a Connect menuitem under the MySQL node. Once choosing Connect, then you
are connected without specifying a database
I agree you should be able to connect without specifying a database, I think this is a bug.
As a workaround, you can click on Direct URL entry and type in "jdbc:mysql://<host>:<port>/"
I forgot to add the Drivers node.
So what I meant is: on the Services tab - Drivers - we right click on a MySQL node and then Connect Using.
Your suggested temporary solution works.
Just want to add, when using the standard port (3306), we can just use "jdbc:mysql://<host>/".
Thanks very much for the workaround.
We are planning to do some changes in this release to (a) make it possible to browse directly to tables from the MySQL
node and (b) list all schemas (aka databases) that the connecting user has rights to view from any connection.
I'm marking this a duplicate of issue 150660 (browse directly to tables from MySQL node), since implementing this
feature will fix this bug.
*** This issue has been marked as a duplicate of 150660 ***