If port is misspecified Retriever fails to fail gracefully

[weecology]

If port is misspecified Retriever fails to fail gracefully

[ethanwhite]

Modified the title to clarify the problem, which is that we don't handle misspecified ports well.

Windows (Postgres): if the port is misspecified the Retriever hangs (before opening) for a long, long, time and when it finally opens it is simply empty (i.e., no datasets available).

Ubuntu (Postgres): loads immediately, but is empty.

Ubuntu (MySQL): works fine, even though it shouldn't. it appears that it's just using the default port anyway.

[ethanwhite]

I don't think that this is a release blocker as it's a serious corner case. Definitely worth handling in the long run though by simply returning an error that the database connection doesn't exist and returning the user to the connection wizard.

[bendmorris]

TODO: create a final page of the connection wizard, which establishes the database connection and only allows the user to move on if it was successful.

[bendmorris]

Resolved: 6545ddf

Now, the connection wizard will not let you continue until it successfully establishes a connection.