PostgreSQL is often set up by default to be at a default port on localhost with the 'postgres' user. It would be useful
to automatically register a connection with these defaults so that in many cases a user can "just connect" to PostgreSQL
out of the box.
Adding MySQL to this, we should do both of them. Also pointed to the UI/Functional spec for this enhancement.
FWIW, -1 from me.
The benefit of registering such connections for a Java user is questionable; the user can register the (correct, not
guessed!) connections himself/herself, it's not a big deal since the driver is already registered. As for users of other
technologies such as Ruby and PHP, what we need to do is make shield JDBC from them, not autodetect some connection and
hope it's the one they want to use.
By the way, how do you know which database is the default when you don't specify one in the connection URL? Do you think
it's common for users to connect without explicitly specifying a database name?
Do you plan to at least check if there is a server running on the default ports before registering the connection? Do
you plan to make sure that if the users deletes the connections, they don't get re-added after restart?
Hi, please review this spec. Thanks!
No comments, so I'm assuming this is OK
Will not be doing PostgreSQL in this release, or if I do I'll make it a separate issue.
Checked in revision a619565a1a7b