DQguru should handle missing/undefined database connections more smoothly (Bugzilla #1582)

Original Description:
The problem is if someone shares a project with another user that 
references a database connection defined in the original user's PL.INI but 
not in the other's, then the other user will run into errors trying to 
connect to a undefined database connection.

Notes:
The solution for handling collaboration will probably follow the Wabit and 
Power*Architect into a server-based solution.

That said, the DQguru could probably be nicer when faced with opening a 
project that contains a database connection defined by someone else. 
Instead of throwing an exception (or at least that's what I recall it 
doing, and I doubt that this has changed), it should do something similar 
to how the Wabit deals with undefined connections in a shared project, in 
that it prompts the user to use one of their own connections to replace it.

Original issue reported on code.google.com by mo.j...@gmail.com on 9 Sep 2009 at 6:50

SQLPower / power-matchmaker

DQguru should handle missing/undefined database connections more smoothly (Bugzilla #1582) #21