Bug #49920 Select Schema in Create/Edit Connection Dialog

Submitted: 24 Dec 2009 17:09 Modified: 28 Dec 2009 10:03
Reporter: Mike Frank Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.11 OS:Any
Assigned to: CPU Architecture:Any

[24 Dec 2009 17:09] Mike Frank
Description:
must know the schema name for input into connection default schema

How to repeat:
create/edit a connection

Suggested fix:
User can type in or click a [...] that pops up the list.
[24 Dec 2009 17:58] Valeriy Kravchuk
Thank you for the feature request.
[28 Dec 2009 10:03] Susanne Ebrecht
Many thanks for writing a feature request.

We are not able to fix/implement this.

For figuring out the schema names you need to connect to the system and ask information_schema.

But what will happen when the database user that you used don't has enough rights here?

A connection before connection setup is made is very risky and a really high security risk.

If you really don't know the database/schema name or if you just create the connection for generate a new database/schema then just let the database/schema field blanc.

On then later communication with the database you always will separately asked for the database/schema anyway.

In almost all features from Workbench the schema name on connection is irrelevant.

The only reason for which you can give here a schema name directly is for the reason that you could start query browser directly and fire statements directly for the schema you filled in at your connection.

So query browser is the only feature for which the schema name could be needed directly. But also there you always first should be able to fire a "Show databases;" and/or "use whatever_name_of_database;"

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.